Triple
T32956540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office Bridge |
E843115
|
entity |
| Predicate | NRHPReferenceArea |
P69674
|
FINISHED |
| Object | Lane County, Oregon |
—
|
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: Lane County, Oregon | Statement: [Office Bridge, NRHPReferenceArea, Lane County, Oregon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NRHPReferenceArea Context triple: [Office Bridge, NRHPReferenceArea, Lane County, Oregon]
-
A.
NRHPArea
chosen
Indicates that an entity is located within, associated with, or part of a designated NRHP (National Register of Historic Places) area.
-
B.
NRHPReference
Indicates that an entity is associated with a specific reference entry or identifier in the National Register of Historic Places.
-
C.
NRHPRegion
Indicates that a place or property is located within a specified National Register of Historic Places (NRHP) region.
-
D.
NRHPReferenceNumber
Indicates the unique identification number assigned to a property or site listed in the National Register of Historic Places.
-
E.
NRHPFocus
Indicates that something is the primary subject or central focus of a listing in the National Register of Historic Places.
- 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_69f3494af2808190ad98cec2f1bc0fe6 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d175fc988190ad4872c9b647b71d |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:21 a.m.