Triple
T27705490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VST |
E698542
|
entity |
| Predicate | operatorAcronym |
P67999
|
FINISHED |
| Object | ESO |
—
|
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: ESO | Statement: [VST, operatorAcronym, ESO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorAcronym Context triple: [VST, operatorAcronym, ESO]
-
A.
operator
Indicates that one entity functions as the operator (controller or handler) of another entity, such as a system, device, or process.
-
B.
operatorAlternativeName
Indicates that an operator has an alternative or alias name by which it may also be known.
-
C.
operatorSymbol
Indicates the symbolic notation used to represent an operator in an expression or formal system.
-
D.
otherOperatorAbbreviation
chosen
Indicates that one operator is referred to or represented by an alternative abbreviated form used by another operator.
-
E.
coreOperator
Indicates that an entity functions as a primary or central operator responsible for executing or managing a core operation within a system or process.
- 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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: April 27, 2026, 2:59 p.m.