Triple
T27700124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Land Shark Stadium |
E698403
|
entity |
| Predicate | primaryTenantDuringName |
P200200
|
FINISHED |
| Object | Miami Dolphins |
—
|
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 Dolphins | Statement: [Land Shark Stadium, primaryTenantDuringName, Miami Dolphins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryTenantDuringName Context triple: [Land Shark Stadium, primaryTenantDuringName, Miami Dolphins]
-
A.
primaryTenantTo
Indicates that one entity serves as the main or principal tenant in relation to another entity, such as a property or lease.
-
B.
primaryTenantFrom
Indicates that one entity serves as the main or principal tenant associated with another entity (such as a property or lease).
-
C.
primaryTenantUntil
Indicates that an entity serves as the main or principal tenant of a property or lease up to a specified end date.
-
D.
primaryTenantRole
Indicates that an entity holds the main or leading tenant role in a tenancy relationship.
-
E.
primaryTenantLevel
Indicates the hierarchical level or rank of a tenant that is designated as the primary or main tenant within a multi-tenant structure.
- 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_69ef590ea74081908f0cd7500d85fa27 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69ff7ae5d088819089aa3b6360b6b749 |
completed | May 9, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69ff7a4df6488190bf60d675b36b1d6d |
completed | May 9, 2026, 6:17 p.m. |
| PDg | Predicate description generation | batch_69ff7ae4bc948190a4cd21a60d091977 |
completed | May 9, 2026, 6:20 p.m. |
Created at: April 27, 2026, 2:56 p.m.