Triple
T18273981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warriors |
E437685
|
entity |
| Predicate | usedByLevel |
P39395
|
FINISHED |
| Object | Division I college sports |
—
|
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: Division I college sports | Statement: [Warriors, usedByLevel, Division I college sports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByLevel Context triple: [Warriors, usedByLevel, Division I college sports]
-
A.
usedForLevelOfPlay
Indicates that something is intended or suitable for a particular level or standard of play.
-
B.
hasUsageLevel
Indicates the degree or intensity with which something is used or utilized.
-
C.
lowerLevelUsedFor
Indicates that a lower-level component, resource, or abstraction is utilized to implement, support, or realize the functionality of a higher-level one.
-
D.
playedAtLevel
chosen
Indicates that an entity participated or performed in an activity, event, or game at a specified level of difficulty, competition, or hierarchy.
-
E.
hasUnitLevel
Indicates that something is associated with, measured at, or applicable to a specific unit level within a larger hierarchy or scale.
- 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5005006108190bbddddbe6bbdc911 |
completed | April 19, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69e44fd81c788190b08c6be3b07a08c5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.