Triple
T9611746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TOPS-20 |
E232117
|
entity |
| Predicate | developer |
P73
|
FINISHED |
| Object | DEC |
E229931
|
NE 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: DEC | Statement: [TOPS-20, developer, DEC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DEC Context triple: [TOPS-20, developer, DEC]
-
A.
DEC
chosen
DEC was the stock ticker symbol for Digital Equipment Corporation, a pioneering American computer company known for its influential minicomputers and contributions to the development of modern computing.
-
B.
DEC
DEC is the New York State agency responsible for conserving, improving, and protecting the state's natural resources and environment.
-
C.
DEC
DEC is a shortened form commonly used to refer to Device Enterprise Communication.
-
D.
De
De is the given name of Zhu De, a prominent Chinese Communist military leader and one of the founders of the People’s Liberation Army.
-
E.
DEN
DEN is the three-letter IATA airport code for Denver International Airport, the primary commercial airport serving Denver, Colorado.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca8485a90c819094fe40b42fde9d70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a87764481909ab96cd2ab96d14b |
completed | April 1, 2026, 10:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d179513f9081909bcd9a456c640ba3 |
completed | April 4, 2026, 8:49 p.m. |
Created at: March 30, 2026, 8:09 p.m.