Triple
T17403120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rogue River Bridge |
E423144
|
entity |
| Predicate | hasRefnum |
P26175
|
FINISHED |
| Object | 05000828 |
—
|
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: 05000828 | Statement: [Rogue River Bridge, hasRefnum, 05000828]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRefnum Context triple: [Rogue River Bridge, hasRefnum, 05000828]
-
A.
refnum
chosen
Indicates that an entity is associated with a specific reference number used to identify or track it.
-
B.
hasReferenceID
Indicates that an entity is associated with a specific reference identifier used to uniquely track or distinguish it.
-
C.
isNumberedBy
Indicates that an entity is assigned, identified, or organized by a specific number or numbering scheme.
-
D.
hasSeriesNumber
Indicates that an entity is assigned a specific ordinal or sequence number within a series or ordered set.
-
E.
isNumbered
Indicates that an entity has been assigned a specific number or position in an ordered sequence.
- 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_69d889d7d27c819088486ce3f0627fa1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43b051cc48190872278ee0b52240d |
completed | April 19, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.