Triple
T29953502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LNER 4771 Green Arrow |
E760832
|
entity |
| Predicate | survivorOfClass |
P168713
|
FINISHED |
| Object | LNER Class V2 |
—
|
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: LNER Class V2 | Statement: [LNER 4771 Green Arrow, survivorOfClass, LNER Class V2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivorOfClass Context triple: [LNER 4771 Green Arrow, survivorOfClass, LNER Class V2]
-
A.
survivorWith
Indicates a relationship where one entity survives an event or condition together with, or in the presence of, another entity.
-
B.
isSurvivorOf
Indicates that one entity has lived through, endured, or remained alive after a particular event, condition, or harmful circumstance involving another entity.
-
C.
survivesBy
Indicates that one entity continues to live or exist after another entity has died or ceased to exist.
-
D.
survivesWith
Indicates that one entity continues to live, endure, or remain viable in the presence, context, or company of another entity.
-
E.
survivesAs
Indicates that one entity continues to exist or persist in place of, or after the end or transformation of, 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_69f2246562b881909d57622f4086d43d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6783880608190906379178b865dc0 |
completed | May 2, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f674df80b08190adb7f7531083bbb1 |
completed | May 2, 2026, 10:04 p.m. |
Created at: April 29, 2026, 6:26 p.m.