Triple
T16644623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boise State Broncos football |
E404434
|
entity |
| Predicate | hasFieldFeature |
P182
|
FINISHED |
| Object | blue turf |
—
|
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: blue turf | Statement: [Boise State Broncos football, hasFieldFeature, blue turf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFieldFeature Context triple: [Boise State Broncos football, hasFieldFeature, blue turf]
-
A.
hasOutfieldFeature
Indicates that an entity possesses or includes a specific feature or characteristic located in its outfield area.
-
B.
hasFeatureID
Indicates that an entity is associated with a specific feature identified by a unique ID.
-
C.
hasFieldContribution
Indicates that an entity has made a contribution or provided input within a particular field, domain, or area of activity.
-
D.
hasFeature
chosen
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
E.
hasFeatureClass
Indicates that an entity is associated with, or categorized under, a particular feature class that characterizes its type or nature.
- 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_69d8838a41f08190b0c3f79c47df5078 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37ad4735c81908a3a227bf02ca489 |
completed | April 18, 2026, 12:36 p.m. |
| PD | Predicate disambiguation | batch_69e296af2f88819092c9ffee4a65d7dd |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:18 a.m.