Triple
T28466022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Badal Mahal |
E720294
|
entity |
| Predicate | locatedInFortComplex |
P112021
|
FINISHED |
| Object | inner complex of Junagarh Fort |
—
|
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: inner complex of Junagarh Fort | Statement: [Badal Mahal, locatedInFortComplex, inner complex of Junagarh Fort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInFortComplex Context triple: [Badal Mahal, locatedInFortComplex, inner complex of Junagarh Fort]
-
A.
locatedInFortress
Indicates that an entity is situated within the boundaries or interior of a fortress.
-
B.
fortressLocation
Indicates that a fortress is located at or in a specified place or geographic area.
-
C.
fortressLocatedOn
Indicates that a fortress is situated on or atop a specified geographic feature, structure, or location.
-
D.
housedWithinComplex
chosen
Indicates that one entity is located inside and functionally part of a larger building or facility complex.
-
E.
fortifiedAsPartOf
Indicates that one entity has been strengthened or reinforced as a component or segment of a larger defensive structure or system.
- 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_69f01a58a67c819097936d9e8da8d6e6 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69ff7bc112088190851501fb2a16103d |
completed | May 9, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69ff7b45507c81909753866ad733601a |
completed | May 9, 2026, 6:21 p.m. |
Created at: April 28, 2026, 2:44 a.m.