Triple
T5749295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawthorne Bridge |
E126808
|
entity |
| Predicate | hasNavigationSpan |
P66514
|
FINISHED |
| Object | center span |
—
|
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: center span | Statement: [Hawthorne Bridge, hasNavigationSpan, center span]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNavigationSpan Context triple: [Hawthorne Bridge, hasNavigationSpan, center span]
-
A.
hasNavigationStatus
Indicates the current state or condition of an entity’s navigation, such as whether and how it is actively navigating.
-
B.
hasNavigationCharacteristic
Indicates that an entity possesses a specific property, feature, or quality related to navigation or navigational behavior.
-
C.
hasNavigationRoute
Indicates that one entity provides or defines a navigation path or route leading to or through another entity.
-
D.
hasNavigationClass
Indicates that an entity is assigned to, or associated with, a particular navigation-related classification or category.
-
E.
hasNavigationUse
Indicates that something is used for navigation or serves a navigational function in relation to another entity.
- 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_69c00832aedc81909899801b141fa3b4 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b52663c8190ab44258468d4296d |
completed | March 22, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c021ca61688190875bd6107161c284 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c02b4ea03c81908c3d799462de20c4 |
completed | March 22, 2026, 5:47 p.m. |
Created at: March 22, 2026, 3:48 p.m.