Triple
T4113904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pio |
E90243
|
entity |
| Predicate | usedAtEventType |
P4341
|
FINISHED |
| Object | college sports games |
—
|
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 games | Statement: [Pio, usedAtEventType, college sports games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAtEventType Context triple: [Pio, usedAtEventType, college sports games]
-
A.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
-
B.
eventUsage
Indicates how an event is employed, applied, or utilized within a particular context or process.
-
C.
associatedEventType
Indicates that one entity is linked to another by the type or category of event with which it is associated.
-
D.
eventUse
Indicates that an event involves the use or utilization of a particular entity (e.g., a resource, tool, or method) as part of its occurrence.
-
E.
usedDuring
chosen
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
- 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_69aed95c080881908125e30c5dcdc6f8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03d7240c8190a64dcbc669772808 |
completed | March 9, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69af0183eb84819087d7184de28f5514 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:41 p.m.