Triple
T19018748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dwarka |
E465425
|
entity |
| Predicate | hasSectorNumbering |
P37553
|
FINISHED |
| Object | sectors 1 to 23 (approximate range) |
—
|
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: sectors 1 to 23 (approximate range) | Statement: [Dwarka, hasSectorNumbering, sectors 1 to 23 (approximate range)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSectorNumbering Context triple: [Dwarka, hasSectorNumbering, sectors 1 to 23 (approximate range)]
-
A.
hasCategoryNumbering
Indicates that an entity is assigned or associated with a specific category-based numbering or index within a classification system.
-
B.
isNumberedBy
chosen
Indicates that an entity is assigned, identified, or organized by a specific number or numbering scheme.
-
C.
hasSeriesNumber
Indicates that an entity is assigned a specific ordinal or sequence number within a series or ordered set.
-
D.
isNumbered
Indicates that an entity has been assigned a specific number or position in an ordered sequence.
-
E.
isSectionNumber
Indicates that one entity is the section number identifier associated with another entity, typically within a structured document or text.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6dd0e6c8190a6dc6af1f7901299 |
completed | April 20, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.