Triple
T3330613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rang Mahal |
E70023
|
entity |
| Predicate | locatedInFortSection |
P40
|
FINISHED |
| Object | southern part of Red Fort palace area |
—
|
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: southern part of Red Fort palace area | Statement: [Rang Mahal, locatedInFortSection, southern part of Red Fort palace area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInFortSection Context triple: [Rang Mahal, locatedInFortSection, southern part of Red Fort palace area]
-
A.
locatedInFortress
Indicates that an entity is situated within the boundaries or interior of a fortress.
-
B.
locatedIn
chosen
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
C.
containsFortress
Indicates that a location or area includes a fortress within its boundaries.
-
D.
locationOfTypeSection
Indicates that a particular location is designated as the section or area associated with a specific type or category.
-
E.
locatedAlong
Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
- 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_69ad85a24f208190bcf83131bfed3521 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb191e1988190a1d88596f6605aff |
completed | March 8, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69ada42c2ba8819091136805ce17b39d |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.