Triple
T28042293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great American Conference |
E708579
|
entity |
| Predicate | memberInstitutionLocation |
P180020
|
FINISHED |
| Object | Arkansas Tech University |
—
|
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: Arkansas Tech University | Statement: [Great American Conference, memberInstitutionLocation, Arkansas Tech University]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberInstitutionLocation Context triple: [Great American Conference, memberInstitutionLocation, Arkansas Tech University]
-
A.
parentInstitutionLocation
Indicates the geographical location associated with a parent institution in relation to another entity.
-
B.
homeInstitutionLocation
Indicates the geographic place where an entity’s primary or home institution is located.
-
C.
locatedAtInstitution
Indicates that an entity is situated at, based in, or physically present within a particular institution.
-
D.
locatedInInstitutionType
Indicates that one entity is situated within, or belongs to, an institution of a specified type.
-
E.
originalInstitutionLocation
Indicates the geographic location where an institution was originally founded or first established.
- F. None of above. chosen
Provenance (4 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_69ef9b6cf538819094a633ffa67afec1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
| PDg | Predicate description generation | batch_69f730890a008190a882f7828f1c9162 |
completed | May 3, 2026, 11:24 a.m. |
Created at: April 27, 2026, 8:26 p.m.