Triple
T26660051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skelly Field at H. A. Chapman Stadium |
E666615
|
entity |
| Predicate | onCampusOf |
P36352
|
FINISHED |
| Object | University of Tulsa |
E49014
|
NE 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: University of Tulsa | Statement: [Skelly Field at H. A. Chapman Stadium, onCampusOf, University of Tulsa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onCampusOf Context triple: [Skelly Field at H. A. Chapman Stadium, onCampusOf, University of Tulsa]
-
A.
hasCampusOn
Indicates that an institution or organization maintains a campus located on a specified geographic area or site.
-
B.
isCampusFor
Indicates that a location serves as the campus associated with a particular institution or organization.
-
C.
isPartOfCampus
chosen
Indicates that one place, facility, or area is located within and belongs to a larger campus.
-
D.
hostsCampusOf
Indicates that one entity serves as the physical location or site where another entity’s campus is situated or maintained.
-
E.
operatesOnCampus
Indicates that an organization or entity conducts its activities or business within the grounds or facilities of a particular campus.
- F. None of above.
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_69ee9cf8c7188190b9b00270a8a89164 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f616be4eb881909246581e38919730 |
completed | May 2, 2026, 3:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a12131984d081909aec251e5c40734a |
completed | May 23, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 2:36 a.m.