Triple
T122358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FieldTurf |
E2475
|
entity |
| Predicate | typicalInstallationSite |
P4119
|
FINISHED |
| Object | outdoor stadiums |
—
|
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: outdoor stadiums | Statement: [FieldTurf, typicalInstallationSite, outdoor stadiums]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalInstallationSite Context triple: [FieldTurf, typicalInstallationSite, outdoor stadiums]
-
A.
typicalDeployment
chosen
Indicates that one entity represents the standard or most commonly used deployment configuration or pattern for the other entity.
-
B.
installedAt
Indicates that something has been set up, placed, or put into operation at a specific location or site.
-
C.
mainLocation
Indicates that one entity serves as the primary or central location associated with another entity.
-
D.
usesLaunchSite
Indicates that an entity conducts or carries out its launches from a particular launch site.
-
E.
formerSiteOf
Indicates that a location previously hosted or contained something (such as a structure, organization, or event) that is no longer present there.
- 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_69a2506c5428819085c28a8884790e29 |
completed | Feb. 28, 2026, 2:18 a.m. |
| NER | Named-entity recognition | batch_69a2573b4e7481909ee09d2899f8a74b |
completed | Feb. 28, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69a2564928208190966a619680a0d6e2 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:24 a.m.