Triple
T8483251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MVS |
E200568
|
entity |
| Predicate | notableComponent |
P7734
|
FINISHED |
| Object | TSO |
E39548
|
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: TSO | Statement: [MVS, notableComponent, TSO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TSO Context triple: [MVS, notableComponent, TSO]
-
A.
TSO
TSO is a major Canadian symphony orchestra based in Toronto, renowned for its performances of classical and contemporary orchestral music.
-
B.
TSO
TSO (The Stationery Office) is a major UK publishing and information services company known for producing and distributing official government and public sector documents.
-
C.
tso
tso is the ISO 639-2 three-letter code for the Tsonga language, a Bantu language spoken primarily in southern Africa.
-
D.
TOS/360
chosen
TOS/360 was an early tape-based operating system developed by IBM for its System/360 mainframe computers, providing basic job control and batch processing capabilities.
-
E.
TOS
TOS is an abbreviation that most commonly refers to "Terms of Service," the rules and conditions governing the use of a service or platform.
- 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_69ca831b17988190a1f3f3413d57b820 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe53845e881909eeb32863c7aa942 |
completed | March 31, 2026, 3:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce3a348a8481908a72c7ac15605022 |
completed | April 2, 2026, 9:43 a.m. |
Created at: March 30, 2026, 6:12 p.m.