Triple
T3047636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyota City |
E83487
|
entity |
| Predicate | sisterCity |
P1072
|
FINISHED |
| Object | Jamshedpur |
E318470
|
NE 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: Jamshedpur | Statement: [Toyota City, sisterCity, Jamshedpur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jamshedpur Context triple: [Toyota City, sisterCity, Jamshedpur]
-
A.
Jamshedpur
chosen
Jamshedpur is a major industrial city in eastern India, best known as the home of Tata Steel and one of the country’s earliest planned company towns.
-
B.
Dhanbad
Dhanbad is a major industrial city in eastern India, widely known as the "Coal Capital of India" for its extensive coal mining operations.
-
C.
Bhilai
Bhilai is an industrial city in central India best known for its large steel plant and planned urban infrastructure.
-
D.
Samastipur
Samastipur is a city in the Indian state of Bihar known as an important railway junction and agricultural trade center in the region.
-
E.
Ranchi
Ranchi is the capital city of the Indian state of Jharkhand, known for its hilly terrain, waterfalls, and role as a regional political and commercial center.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ad8b24924c8190a9bb6f61d519e4ae |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9bad11b48190a5bd01e91a320e14 |
completed | March 8, 2026, 3:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b224b717e081909462645d78b33cc9 |
completed | March 12, 2026, 2:28 a.m. |
Created at: March 8, 2026, 3:01 p.m.