Triple
T3735416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Musi River |
E79170
|
entity |
| Predicate | historicallyShaped |
P16345
|
FINISHED |
| Object | urban development of Hyderabad |
—
|
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: urban development of Hyderabad | Statement: [Musi River, historicallyShaped, urban development of Hyderabad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyShaped Context triple: [Musi River, historicallyShaped, urban development of Hyderabad]
-
A.
historicallyIn
Indicates that one entity existed, occurred, or was situated within the historical context, period, or jurisdiction associated with another entity.
-
B.
historicallyConsidered
Indicates that one entity has been regarded or classified in a particular way relative to another entity during a past historical period.
-
C.
historicalForm
Indicates that one entity is an earlier or historically attested form or variant of another entity.
-
D.
historicallyGivenIn
Indicates that something was customarily or traditionally granted, presented, or assigned to something or someone in the past.
-
E.
historicallyLinked
chosen
Indicates that two entities are connected through a shared or related historical event, period, or development.
- 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_69ad8b0e4650819090ad7cef094285e8 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb3b399c819091b42209925c0d8f |
completed | March 8, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69adc04746588190b0dc535638f23546 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.