Triple
T1056266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCAA Division II men's basketball coaches |
E22801
|
entity |
| Predicate | typicalWorkLocation |
P1527
|
FINISHED |
| Object | campus athletic facilities |
—
|
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: campus athletic facilities | Statement: [NCAA Division II men's basketball coaches, typicalWorkLocation, campus athletic facilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalWorkLocation Context triple: [NCAA Division II men's basketball coaches, typicalWorkLocation, campus athletic facilities]
-
A.
recruitmentLocation
Indicates the place or geographic area where the recruitment or hiring of individuals occurs.
-
B.
locationOfWork
chosen
Indicates the place or site where an entity performs its work or carries out its professional activities.
-
C.
typicalUseLocation
Indicates the usual or most common location where an entity is used or operates.
-
D.
locatedOff
Indicates that one entity is situated away from, but in the vicinity of, another entity or reference point, rather than directly on or within it.
-
E.
positionInWork
Indicates the specific role, rank, or placement an entity holds within a larger work or structured composition.
- 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_69a493dada0481909c43649f9843ea91 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8d9102c819090af78cae50f0ff2 |
completed | March 1, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69a4b731e25c8190b5ea8466648c2c9a |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.