Triple
T4456410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miami Orange Bowl |
E97735
|
entity |
| Predicate | teamTenancyStart |
P38713
|
FINISHED |
| Object | Miami Dolphins 1966 |
—
|
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: Miami Dolphins 1966 | Statement: [Miami Orange Bowl, teamTenancyStart, Miami Dolphins 1966]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamTenancyStart Context triple: [Miami Orange Bowl, teamTenancyStart, Miami Dolphins 1966]
-
A.
tenantsStart
Indicates that a tenancy relationship begins or is initiated at a specific time or event.
-
B.
sportsTeamTenancyStart
chosen
Indicates the date or point in time when an entity begins its occupancy or tenure as a sports team at a particular venue or location.
-
C.
majorTeamTenant
Indicates that a major sports team is the primary tenant or long-term occupant of a particular venue or facility.
-
D.
mainTenant
Indicates that the subject is the primary tenant responsible for a property or rental agreement, as opposed to a subtenant or secondary occupant.
-
E.
teamContext
Indicates that an entity is considered or interpreted within the scope, structure, or circumstances of a particular team.
- 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_69b3454777808190b78aa9047ba1f018 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3564216b081908c41109100b36862 |
completed | March 13, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69b34f649df081909d3cc2f6a1b8f282 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:33 p.m.