Triple
T24422761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T-Model |
E615768
|
entity |
| Predicate | usedInLevel |
P127298
|
FINISHED |
| Object | top-level international competitions |
—
|
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: top-level international competitions | Statement: [T-Model, usedInLevel, top-level international competitions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInLevel Context triple: [T-Model, usedInLevel, top-level international competitions]
-
A.
usedInStructure
Indicates that something (such as a material, component, or element) is employed as part of the composition or construction of a larger structure.
-
B.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
C.
usedInStage
Indicates that something is utilized or applied during a particular stage or phase of a process or workflow.
-
D.
usedInRoom
Indicates that something is utilized or functions within a particular room or enclosed space.
-
E.
usedForLevelOfPlay
chosen
Indicates that something is intended or suitable for a particular level or standard of play.
- 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_69e2d7eadb248190a867130fe45f0388 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f296a4285881909376560f1cf4bf62 |
completed | April 29, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:14 a.m.