Triple
T28417993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karan Mahal |
E719862
|
entity |
| Predicate | locatedWithinFort |
P28661
|
FINISHED |
| Object | Junagarh Fort |
—
|
NE NERFINISHED |
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: Junagarh Fort | Statement: [Karan Mahal, locatedWithinFort, Junagarh Fort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedWithinFort Context triple: [Karan Mahal, locatedWithinFort, Junagarh Fort]
-
A.
locatedInFortress
chosen
Indicates that an entity is situated within the boundaries or interior of a fortress.
-
B.
withinFortifications
Indicates that one entity is located inside the defensive structures or fortifications of another entity.
-
C.
isInFortifiedTown
Indicates that an entity is located within a town that is protected by defensive structures or fortifications.
-
D.
fortressLocation
Indicates that a fortress is located at or in a specified place or geographic area.
-
E.
stateOfFort
Indicates that a specified attribute or condition describes the current status or situation of a fort.
- 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_69eff6f1c5088190bc24bfbf92f9c017 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69ff795d25d08190b7584c72be39d309 |
completed | May 9, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69ff78a90fbc8190a62c57456dc1d4ad |
completed | May 9, 2026, 6:10 p.m. |
Created at: April 28, 2026, 1:31 a.m.