Triple
T29203554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alstom Class 460 |
E740345
|
entity |
| Predicate | operatorBeforeRebuild |
P198673
|
FINISHED |
| Object | Gatwick Express franchise |
—
|
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: Gatwick Express franchise | Statement: [Alstom Class 460, operatorBeforeRebuild, Gatwick Express franchise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorBeforeRebuild Context triple: [Alstom Class 460, operatorBeforeRebuild, Gatwick Express franchise]
-
A.
laterRebuiltAs
Indicates that one entity was reconstructed or redeveloped at a later time to become or be replaced by another specific entity.
-
B.
safetyIssueBeforeRebuild
Indicates that a safety-related problem existed prior to a rebuild or reconstruction event.
-
C.
rebuild
Indicates restoring or constructing again something that was previously built, often after damage, destruction, or significant alteration.
-
D.
operatorBeforeConflict
Indicates that an operator performed or was in place before a specified conflict occurred or was identified.
-
E.
constructedBefore
Indicates that one entity was built or created at an earlier time than another entity.
- F. None of above. chosen
Provenance (4 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_69f07cb974108190b7e86ca489a6ebb6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fefb15220081908da36aac386fa582 |
completed | May 9, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69fefa8e8ad48190a723fed81e9d64d0 |
completed | May 9, 2026, 9:12 a.m. |
| PDg | Predicate description generation | batch_69fefb13eb288190bcfae0541cfd7b98 |
completed | May 9, 2026, 9:15 a.m. |
Created at: April 28, 2026, 12:08 p.m.