Triple
T26509293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forth Road Bridge steelwork (contractor) |
E669633
|
entity |
| Predicate | contractorHeadquarters |
P10544
|
FINISHED |
| Object | Glasgow |
—
|
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: Glasgow | Statement: [Forth Road Bridge steelwork (contractor), contractorHeadquarters, Glasgow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contractorHeadquarters Context triple: [Forth Road Bridge steelwork (contractor), contractorHeadquarters, Glasgow]
-
A.
architecturalFirmHeadquarters
Indicates the location where an architectural firm’s main offices or central headquarters are based.
-
B.
employerHeadquarters
chosen
Indicates the location where an employer’s main corporate offices or central administrative operations are based.
-
C.
hasHeadquartersFunctionFor
Indicates that an entity serves as the central coordinating or managing headquarters for another entity’s operations or activities.
-
D.
headquarteredWith
Indicates that two entities share the same headquarters location.
-
E.
headquartersAt
Indicates that an organization’s main administrative center or primary office is located at a specified place.
- 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 27, 2026, 1:19 a.m.