Triple
T10896390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 40 |
E257319
|
entity |
| Predicate | originalNumberingSystem |
P5213
|
FINISHED |
| Object | D200–D399 |
—
|
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: D200–D399 | Statement: [British Rail Class 40, originalNumberingSystem, D200–D399]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalNumberingSystem Context triple: [British Rail Class 40, originalNumberingSystem, D200–D399]
-
A.
numberingSystemBasedOn
Indicates that one numbering system is derived from, structured according to, or conceptually dependent on another numbering system.
-
B.
hasNumberSystem
chosen
Indicates that an entity possesses or uses a particular system for representing and organizing numbers.
-
C.
usesNumeralsFrom
Indicates that one writing system, notation, or representation employs the numeral symbols originating from another system.
-
D.
notationSystem
Indicates a relationship where one entity is the system or method of notation used to represent or encode another entity.
-
E.
scripturalNumberingSystem
Indicates a relationship where a particular numbering system is used to organize, reference, or index passages within a scriptural text.
- 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75d022f4c81909cd9ea27a9f0cd32 |
completed | April 9, 2026, 8:02 a.m. |
| PD | Predicate disambiguation | batch_69d70d3943c881908895397eccc3e415 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.