Triple
T11820377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AT&T Field |
E281108
|
entity |
| Predicate | notableTenantLevel |
P29691
|
FINISHED |
| Object | Double-A |
—
|
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: Double-A | Statement: [AT&T Field, notableTenantLevel, Double-A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTenantLevel Context triple: [AT&T Field, notableTenantLevel, Double-A]
-
A.
notableTenant
Indicates that an entity is or has been a significant or noteworthy occupant or renter of a particular place or property.
-
B.
primaryTenantLevel
Indicates the hierarchical level or rank of a tenant that is designated as the primary or main tenant within a multi-tenant structure.
-
C.
mainTenant
Indicates that the subject is the primary tenant responsible for a property or rental agreement, as opposed to a subtenant or secondary occupant.
-
D.
intendedTenant
Indicates that one entity is designated or expected to occupy or lease another entity (such as a property) as a tenant.
-
E.
leagueLevelOfTenant
chosen
Indicates the competitive league tier or division in which the tenant entity participates or is classified.
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5e87e488190905bc3bb6d721e56 |
completed | April 10, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.