Triple
T31589191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kenan family |
E806041
|
entity |
| Predicate | buildingNamesake |
P68977
|
FINISHED |
| Object | Kenan Stadium at UNC-Chapel Hill |
—
|
NE NERFINISHED |
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: Kenan Stadium at UNC-Chapel Hill | Statement: [Kenan family, buildingNamesake, Kenan Stadium at UNC-Chapel Hill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingNamesake Context triple: [Kenan family, buildingNamesake, Kenan Stadium at UNC-Chapel Hill]
-
A.
buildingNamed
Indicates that a particular building is known or referred to by a specified name.
-
B.
notablePlaceNamedAfter
chosen
Indicates that a notable place (such as a city, building, or landmark) is named in honor of or derived from the name of a particular entity.
-
C.
houseNamedAfter
Indicates that a house or building bears a name derived from or in honor of a particular person, place, event, or entity.
-
D.
notableAsNamesakeOf
Indicates that one entity is recognized or distinguished specifically for being the namesake of another entity.
-
E.
hasPlaceNamedAfter
Indicates that one place is named in honor of or derived from the name of another place.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a82eb2848190b5329618001a90fd |
completed | May 3, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:27 p.m.