Triple
T25115686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burari |
E629121
|
entity |
| Predicate | hasPincodeAreaName |
P920
|
FINISHED |
| Object | Burari |
—
|
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: Burari | Statement: [Burari, hasPincodeAreaName, Burari]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPincodeAreaName Context triple: [Burari, hasPincodeAreaName, Burari]
-
A.
hasCouncilAreaName
Indicates that an entity is associated with a council area identified by a specific name.
-
B.
hasCouncilAreaCode
Indicates that an entity is associated with a specific council area identified by a particular code.
-
C.
postalAreaIncludes
Indicates that a given postal area geographically contains or covers another specified location or region.
-
D.
postalArea
chosen
Indicates that one entity is the postal or ZIP code area associated with the location or address represented by the other entity.
-
E.
hasPINCode
Indicates that an entity is associated with or assigned a specific personal identification number (PIN) code.
- 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_69e2ff3169d08190973b6061d5009abd |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f465c66cc48190b66b14e4b9036432 |
completed | May 1, 2026, 8:35 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:27 a.m.