Triple
T9095421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trowse Swing Bridge |
E218005
|
entity |
| Predicate | transportModeCarried |
P1379
|
FINISHED |
| Object | rail |
—
|
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: rail | Statement: [Trowse Swing Bridge, transportModeCarried, rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportModeCarried Context triple: [Trowse Swing Bridge, transportModeCarried, rail]
-
A.
transportModePresent
Indicates that a particular mode of transportation is involved or available in the described context or event.
-
B.
transportType
chosen
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
C.
transportRole
Indicates that an entity participates in a transportation process with a specific functional role (e.g., carrier, passenger, cargo, or operator).
-
D.
transportModeImportant
Indicates that the mode of transport used is considered significant or plays an important role in the context of the relationship or action.
-
E.
transportAssumption
Indicates an assumption that something can be transported or carried from one place or context to another.
- 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_69ca83d9844081908e561e367fda6d45 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc96b650648190a8f59cee402d12aa |
completed | April 1, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69cc65fc7f408190a5846e29ab3b97e5 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:14 p.m.