Triple
T29953603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LNER Class V2 |
E760834
|
entity |
| Predicate | museumDisplayOfGreenArrow |
P168293
|
FINISHED |
| Object | National Railway Museum |
—
|
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: National Railway Museum | Statement: [LNER Class V2, museumDisplayOfGreenArrow, National Railway Museum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: museumDisplayOfGreenArrow Context triple: [LNER Class V2, museumDisplayOfGreenArrow, National Railway Museum]
-
A.
museumDisplayType
Indicates the manner or format in which items are presented or exhibited within a museum setting.
-
B.
orientationInMuseum
Indicates the spatial positioning or directional arrangement of an object or exhibit within a museum space.
-
C.
museumHolds
Indicates that a museum possesses, preserves, or has custody of a particular item or collection within its holdings.
-
D.
museumAt
Indicates that an entity (such as an exhibit, artifact, or event) is located at or associated with a particular museum.
-
E.
exhibitedBy
Indicates that something (such as a quality, behavior, or characteristic) is shown, displayed, or demonstrated by a particular 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_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 6:26 p.m.