Triple
T14870365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tso |
E349726
|
entity |
| Predicate | usedAsSubtag |
P2506
|
FINISHED |
| Object | tso |
—
|
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: tso | Statement: [tso, usedAsSubtag, tso]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsSubtag Context triple: [tso, usedAsSubtag, tso]
-
A.
isSubdivisionUsedFor
Indicates that a particular subdivision (such as a region, section, or part of something) is utilized for a specified purpose or function.
-
B.
usedAsPrefixIn
Indicates that one element functions as a leading prefix component in the formation or representation of another element.
-
C.
isUsedAs
chosen
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
D.
isUsedUnder
Indicates that one entity is utilized or applied within the context, conditions, or framework defined by another entity.
-
E.
usesSubgroup
Indicates that one entity employs, incorporates, or operates through a specific subgroup of another entity or system.
- 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_69d822ee4f408190b6ac3b2fa434f0df |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded57967748190a7c05ebb74aacb7c |
completed | April 15, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69de8c1798c08190b433e9ad21e41a42 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:55 a.m.