Triple
T29425830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andre Reed Stadium |
E746290
|
entity |
| Predicate | isInConference |
P2672
|
FINISHED |
| Object | Pennsylvania State Athletic Conference |
—
|
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: Pennsylvania State Athletic Conference | Statement: [Andre Reed Stadium, isInConference, Pennsylvania State Athletic Conference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInConference Context triple: [Andre Reed Stadium, isInConference, Pennsylvania State Athletic Conference]
-
A.
isPowerConference
Indicates that an athletic conference is considered a major or elite "power" conference within its sport or league.
-
B.
hasConference
chosen
Indicates that an entity organizes, hosts, or is associated with a specific conference.
-
C.
isConferenceSpecific
Indicates that something applies only within the context of a particular conference and does not hold generally outside that specific event.
-
D.
hasConferenceType
Indicates that an entity is associated with or classified by a specific type or category of conference.
-
E.
hasConferenceSystem
Indicates that an entity is equipped with or utilizes a particular conference or conferencing system.
- 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_69f0a7a06e0081908add494075912eb4 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a6ca4188190acb905faee93f5d1 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 3:09 p.m.