Triple
T32549827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pahokee High School |
E831942
|
entity |
| Predicate | playsInRivalryGame |
P87828
|
FINISHED |
| Object | Muck Bowl |
—
|
NE NERFINISHED |
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: Muck Bowl | Statement: [Pahokee High School, playsInRivalryGame, Muck Bowl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsInRivalryGame Context triple: [Pahokee High School, playsInRivalryGame, Muck Bowl]
-
A.
playsRivalryGameAgainst
Indicates that one entity participates in a rivalry game as an opponent against another entity.
-
B.
associatedWithRivalryGame
chosen
Indicates that there is a connection or involvement between entities specifically in the context of a rivalry game.
-
C.
hasHomeStadiumInRivalry
Indicates that one entity’s home stadium is the venue used when it participates in a rivalry with another entity.
-
D.
associatedRivalry
Indicates a relationship where one entity is linked to another as its rival, competitor, or opposing counterpart.
-
E.
hasRivalrySport
Indicates a competitive relationship in which two entities are rivals specifically within the context of a sport or sporting activity.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 1:02 a.m.