Triple
T24312057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago street network |
E612700
|
entity |
| Predicate | hasNumberingIncrement |
P155521
|
FINISHED |
| Object | 800 address numbers per mile |
—
|
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: 800 address numbers per mile | Statement: [Chicago street network, hasNumberingIncrement, 800 address numbers per mile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberingIncrement Context triple: [Chicago street network, hasNumberingIncrement, 800 address numbers per mile]
-
A.
hasNumberingStart
Indicates that an ordered sequence or list begins at a specified starting number or position.
-
B.
hasNumberingRole
Indicates that an entity holds a specific role or responsibility related to assigning, managing, or using numbers within a given context.
-
C.
hasNumberingWithin
Indicates that one entity assigns or follows a specific numbering scheme within the scope or structure of another entity.
-
D.
isNumberedBy
Indicates that an entity is assigned, identified, or organized by a specific number or numbering scheme.
-
E.
hasCategoryNumbering
Indicates that an entity is assigned or associated with a specific category-based numbering or index within a classification system.
- F. None of above. chosen
Provenance (4 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_69e2d7d91bb48190bc5377d17a85fb21 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2922b867c8190a6bf2adbfb68a584 |
completed | April 29, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69f1c45f45888190a9ccc225906c34bd |
completed | April 29, 2026, 8:42 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 18, 2026, 1:43 a.m.