Triple
T27700102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Land Shark Stadium |
E698403
|
entity |
| Predicate | homeTeamDuringName |
P163940
|
FINISHED |
| Object | Miami Hurricanes football |
—
|
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: Miami Hurricanes football | Statement: [Land Shark Stadium, homeTeamDuringName, Miami Hurricanes football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeTeamDuringName Context triple: [Land Shark Stadium, homeTeamDuringName, Miami Hurricanes football]
-
A.
homeTeamDuringName
chosen
Indicates that an entity serves as the designated home team during a specified named event or period.
-
B.
homeTeam
Indicates that one entity is designated as the home team in a game, match, or sporting event involving another entity.
-
C.
homeTeamChampion
Indicates that the team playing at home is the champion or title-holding team in the given context.
-
D.
hostTeam
Indicates that one team serves as the host (home) team in relation to a particular game, match, or event.
-
E.
homeTeamUntil
Indicates that an entity serves as the home team for another entity up to (but not necessarily after) a specified time or event.
- 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_69ef590ea74081908f0cd7500d85fa27 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 2:56 p.m.