Triple
T8394515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LNER Class A3 4472 Flying Scotsman |
E198020
|
entity |
| Predicate | worksNumber |
P81991
|
FINISHED |
| Object | 1564 |
—
|
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: 1564 | Statement: [LNER Class A3 4472 Flying Scotsman, worksNumber, 1564]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksNumber Context triple: [LNER Class A3 4472 Flying Scotsman, worksNumber, 1564]
-
A.
workNumbering
Indicates that a specific numbering or cataloging identifier is assigned to a work within a larger collection or system.
-
B.
workNumberInSet
Indicates that a particular work number belongs to, or is included within, a specified set of work numbers.
-
C.
appearsInWorkNumber
Indicates that an entity is featured or occurs within a specific numbered work in a series or collection.
-
D.
numberOfWorks
Indicates the total count of works associated with a given entity.
-
E.
worksOver
Indicates that one entity performs work that extends beyond or exceeds a certain limit, threshold, or standard associated with 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_69ca82f816bc8190ab321c07d72208c1 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb8185ef60819085cfa7491d35834a |
completed | March 31, 2026, 8:10 a.m. |
| PD | Predicate disambiguation | batch_69cb70d24b248190a326aa6804f942b5 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb77690720819099de1e22b84a9563 |
completed | March 31, 2026, 7:27 a.m. |
Created at: March 30, 2026, 6:03 p.m.