Triple
T15047327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barry Alvarez Field |
E379262
|
entity |
| Predicate | isNamingFeatureOf |
P99932
|
FINISHED |
| Object | Camp Randall Stadium playing surface |
—
|
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: Camp Randall Stadium playing surface | Statement: [Barry Alvarez Field, isNamingFeatureOf, Camp Randall Stadium playing surface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNamingFeatureOf Context triple: [Barry Alvarez Field, isNamingFeatureOf, Camp Randall Stadium playing surface]
-
A.
isFeatureOf
Indicates that something functions as a characteristic, attribute, or component belonging to or describing another entity.
-
B.
namedForFeature
Indicates that one entity is named after, or derives its name from, a particular feature or characteristic of another entity.
-
C.
hasNaming
Indicates that one entity assigns, bears, or is associated with a specific name or designation provided by another entity.
-
D.
namedFeature
Indicates that an entity has a specific feature or attribute that is explicitly given a name.
-
E.
hasNamesakeFeature
chosen
Indicates that one entity has a feature (such as a place, object, or structure) that is named after another entity.
- 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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69deda8e64e48190873104a02a676ff3 |
completed | April 15, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69de9a69d7848190b2b4662dd30f20e9 |
completed | April 14, 2026, 7:50 p.m. |
Created at: April 10, 2026, 3 a.m.