Triple
T38429448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D400–D449 |
E903757
|
entity |
| Predicate | successorNumberingScheme |
P96282
|
FINISHED |
| Object | Class 50 TOPS numbers |
—
|
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: Class 50 TOPS numbers | Statement: [D400–D449, successorNumberingScheme, Class 50 TOPS numbers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorNumberingScheme Context triple: [D400–D449, successorNumberingScheme, Class 50 TOPS numbers]
-
A.
historicalNumberingScheme
Indicates that the associated numbering system or identifier reflects a past or legacy scheme that was used historically rather than the current one.
-
B.
standardNumberingScheme
Indicates that there is a specific, commonly accepted numbering system or convention being applied to identify or order the related entities.
-
C.
laterNumberingSystem
chosen
Indicates that one numbering system was adopted or used after another, reflecting a subsequent or more recent scheme of numbering.
-
D.
successorCode
Indicates that one code directly follows and replaces another code in a defined sequence or versioning scheme.
-
E.
followsNumbering
Indicates that one entity adheres to or continues the numbering sequence established by another entity.
- 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a0117b6539c8190be7d231e891fe546 |
completed | May 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_6a011762f7ec8190afc884b92419d33f |
completed | May 10, 2026, 11:40 p.m. |
Created at: May 3, 2026, 4:31 p.m.