Triple
T16501322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun Bowl |
E400805
|
entity |
| Predicate | originalParticipantsType |
P123794
|
FINISHED |
| Object | high school teams |
—
|
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: high school teams | Statement: [Sun Bowl, originalParticipantsType, high school teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalParticipantsType Context triple: [Sun Bowl, originalParticipantsType, high school teams]
-
A.
participantType
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
-
B.
previousParticipantsFormat
Indicates that there is a specific way or structure in which information about prior participants is represented or recorded.
-
C.
supportsParticipantType
Indicates that an entity is compatible with, or designed to work with, a specified type or category of participant.
-
D.
hasParticipants
Indicates that an event, activity, or situation involves one or more entities as participants in it.
-
E.
participantFrom
Indicates that a participant originates from, is associated with, or comes out of a specified source, group, or context.
- F. None of above. chosen
Provenance (4 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e4f7b7c8190adb5a113f798484f |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:14 a.m.