Triple
T38429457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D400–D449 |
E903757
|
entity |
| Predicate | preTOPSClassDesignation |
P68918
|
FINISHED |
| Object | D400 series |
—
|
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: D400 series | Statement: [D400–D449, preTOPSClassDesignation, D400 series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preTOPSClassDesignation Context triple: [D400–D449, preTOPSClassDesignation, D400 series]
-
A.
preTOPSDesignation
chosen
Indicates that an entity has been assigned a preliminary or provisional TOPS (Total Operations Processing System) designation within a classification or tracking system.
-
B.
prototypeDesignation
Indicates that one entity is designated or identified as a prototype version or exemplar of another entity.
-
C.
typicalDesignation
Indicates that one entity is the usual or commonly used designation (name, label, or title) for another entity.
-
D.
topClass
Indicates that an entity is the most general or highest-level class in a classification or hierarchy, with all other classes falling under it.
-
E.
systemDesignation
Indicates that an entity has been assigned a specific formal label or identifier within a defined system or framework.
- 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_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.