Triple
T2058298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cameron Indoor Stadium |
E45727
|
entity |
| Predicate | hasTenantsSince |
P3320
|
FINISHED |
| Object | Duke Blue Devils men's basketball since 1940 |
—
|
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: Duke Blue Devils men's basketball since 1940 | Statement: [Cameron Indoor Stadium, hasTenantsSince, Duke Blue Devils men's basketball since 1940]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTenantsSince Context triple: [Cameron Indoor Stadium, hasTenantsSince, Duke Blue Devils men's basketball since 1940]
-
A.
hasTenantSince
chosen
Indicates that an entity has been the tenant of another entity starting from a specified point in time.
-
B.
hasTenants
Indicates that an entity occupies or rents space from another entity as its tenant.
-
C.
existsSince
Indicates that an entity has been in existence or valid from a specified point in time onward.
-
D.
numberOfAnchorTenants
Indicates the count of primary or major tenants associated with a given property or location.
-
E.
hasLongTermDatasetSince
Indicates that an entity has maintained or used a particular dataset continuously starting from a specified point in time.
- 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_69a8891a19508190a12ef1e192308dcb |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9ae0130819089f7d62005466a45 |
completed | March 7, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_69abb7ad5a7c8190b92575d6053b3fb7 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:40 p.m.