Triple
T13591769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shri Ram Janmabhoomi Teerth Kshetra Trust |
E324707
|
entity |
| Predicate | managesPropertyType |
P51437
|
FINISHED |
| Object | temple |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: temple | Statement: [Shri Ram Janmabhoomi Teerth Kshetra Trust, managesPropertyType, temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesPropertyType Context triple: [Shri Ram Janmabhoomi Teerth Kshetra Trust, managesPropertyType, temple]
-
A.
managesPropertyFor
Indicates that one entity is responsible for overseeing, operating, or administering a property on behalf of another entity.
-
B.
propertyTypeOwned
Indicates that one entity owns a specific type or category of property in relation to another entity.
-
C.
typeOfPropertyManaged
chosen
Indicates the specific category or kind of property that an entity is responsible for managing.
-
D.
estateManagementActivity
Indicates activities involved in administering, maintaining, or overseeing an estate or property and its associated affairs.
-
E.
propertyTypeMix
Indicates that an entity involves or consists of a combination of different types of properties rather than a single uniform property type.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb056ce088190a6feb4266633d18b |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:49 p.m.