Triple
T27746947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sector III, Salt Lake |
E702008
|
entity |
| Predicate | plannedTownship |
P97765
|
FINISHED |
| Object | Salt Lake City, Kolkata |
—
|
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: Salt Lake City, Kolkata | Statement: [Sector III, Salt Lake, plannedTownship, Salt Lake City, Kolkata]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedTownship Context triple: [Sector III, Salt Lake, plannedTownship, Salt Lake City, Kolkata]
-
A.
townPlannedWith
Indicates that a town was designed, organized, or laid out in coordination with a particular plan, entity, or planning effort.
-
B.
isPlannedTown
chosen
Indicates that a town has been deliberately designed and constructed according to a pre-established plan rather than developing organically over time.
-
C.
locatedInPlannedTown
Indicates that an entity is situated within the boundaries of a town that has been deliberately planned or designed rather than having developed organically.
-
D.
plannedDevelopment
Indicates that one entity has been designated or scheduled for future development or construction by another entity.
-
E.
hasPlannedCommunity
Indicates that an entity is associated with or contains a community that has been intentionally designed and organized according to a specific development plan.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 27, 2026, 4:16 p.m.