Triple
T8363391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whistler |
E197063
|
entity |
| Predicate | buildNumberExample |
P11583
|
FINISHED |
| Object | Build 2202 |
—
|
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: Build 2202 | Statement: [Whistler, buildNumberExample, Build 2202]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildNumberExample Context triple: [Whistler, buildNumberExample, Build 2202]
-
A.
numberBuilt
Indicates the total count of items or structures that have been constructed or produced.
-
B.
buildingNumber
Indicates the specific numeric identifier assigned to a building within an address or location.
-
C.
builderModelCode
Indicates that one entity is identified as the specific model code used by a builder or construction-related system for another entity.
-
D.
hasVersionNumber
chosen
Indicates that an entity is associated with a specific version identifier or number.
-
E.
projectNumber
Indicates a relationship where a specific identifying number is assigned to or associated with a particular project.
- 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_69ca82f2dbe48190aba982e75a0d94de |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80768b208190a5f6c9e6cb6e7f30 |
completed | March 31, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69cb70cd04b08190ab5f72afd22a7967 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6 p.m.