Triple
T13023663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California State Route 275 |
E326242
|
entity |
| Predicate | towerBridgeStatus |
P82990
|
FINISHED |
| Object | historic landmark |
—
|
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: historic landmark | Statement: [California State Route 275, towerBridgeStatus, historic landmark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: towerBridgeStatus Context triple: [California State Route 275, towerBridgeStatus, historic landmark]
-
A.
towerStatus
chosen
Indicates the current operational or structural condition of a tower within a given system or context.
-
B.
cityTerminalStatus
Indicates the operational or functional status of a city’s terminal (such as an airport, bus, or train terminal) within a given context or system.
-
C.
topFlightStatus
Indicates the current operational or service status assigned to a flight within a top-level or primary flight schedule.
-
D.
towerManagedBy
Indicates that a particular tower is under the control, supervision, or administrative responsibility of a specified managing entity.
-
E.
airportStatus
Indicates the current operational condition or state of an airport (e.g., open, closed, delayed, restricted).
- 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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97ed05e9c8190a4f208662bca0602 |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc39a0881908119c62e31bf6182 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:52 p.m.