Triple
T1325133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forth Bridge (rail, south end) |
E28308
|
entity |
| Predicate | operatorRegion |
P6665
|
FINISHED |
| Object | ScotRail service 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: ScotRail service area | Statement: [Forth Bridge (rail, south end), operatorRegion, ScotRail service area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorRegion Context triple: [Forth Bridge (rail, south end), operatorRegion, ScotRail service area]
-
A.
operatesToRegion
Indicates that an agent conducts operations or provides services directed toward or within a specified region.
-
B.
operatedInRegion
chosen
Indicates that an entity conducted operations or activities within a specified geographic region.
-
C.
marketRegion
Indicates the geographic or demographic area in which a product, service, or entity is actively marketed or targeted.
-
D.
endpointRegion
Indicates that one entity serves as the geographic or logical region in which the other entity’s endpoint is located or configured.
-
E.
landingRegion
Indicates the area or zone where an object or entity comes to rest or makes contact after moving or descending.
- 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_69a498540a2481909e807a762280d3ba |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c19e81c0819092f85201ae34422a |
completed | March 1, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69a4beedb49c8190beb5b85cdda05013 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.