Triple
T13123037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 10 bridge over Escambia Bay |
E311772
|
entity |
| Predicate | approachFromWest |
P31133
|
FINISHED |
| Object | Pensacola area |
—
|
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: Pensacola area | Statement: [Interstate 10 bridge over Escambia Bay, approachFromWest, Pensacola area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approachFromWest Context triple: [Interstate 10 bridge over Escambia Bay, approachFromWest, Pensacola area]
-
A.
approachDirection
chosen
Indicates the direction or bearing from which one entity moves closer to or advances toward another entity.
-
B.
startingForwardWest
Indicates that an entity begins moving or facing in the forward direction toward the west.
-
C.
southernApproachNear
Indicates that one entity is located near the southern approach or access route of another entity.
-
D.
approachRoute
Indicates the path or method taken by one entity as it moves toward or comes closer to another entity or target.
-
E.
approachOver
Indicates that one entity moves closer to another entity from a position above or higher than it.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9819840b881909b76022b4c4dcaed |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98043a74c81908648e6cd0b4c7f71 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:07 p.m.