Triple
T26035582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De Anza College Stadium |
E647541
|
entity |
| Predicate | usedForLevel |
P127298
|
FINISHED |
| Object | 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: college sports | Statement: [De Anza College Stadium, usedForLevel, college sports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForLevel Context triple: [De Anza College Stadium, usedForLevel, college sports]
-
A.
usedForLevelOfPlay
chosen
Indicates that something is intended or suitable for a particular level or standard of play.
-
B.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
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.
hasUsageLevel
Indicates the degree or intensity with which something is used or utilized.
-
E.
lowerLevelCurrentlyUsedFor
Indicates that a lower level or subordinate layer is presently being utilized for a particular purpose or function.
- 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_69e77e8c88f08190858c4c81bd2e1b9a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 22, 2026, 9:07 a.m.