Triple
T17663876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princeton Tigers men’s cross country |
E440320
|
entity |
| Predicate | trainingFacilities |
P9852
|
FINISHED |
| Object | Princeton University campus 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: Princeton University campus facilities | Statement: [Princeton Tigers men’s cross country, trainingFacilities, Princeton University campus facilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trainingFacilities Context triple: [Princeton Tigers men’s cross country, trainingFacilities, Princeton University campus facilities]
-
A.
trainingFacilityLocation
chosen
Indicates the place or site where a training facility is situated or operates.
-
B.
trainingStations
Indicates a relationship where certain locations or facilities serve as designated sites for training activities or instruction.
-
C.
trainingLocationType
Indicates the type or category of place where a training activity occurs.
-
D.
trainingClub
Indicates that one entity serves as a club or organization where the other entity receives training.
-
E.
trainingCamps
Indicates that one entity organizes, hosts, or is associated with training camps for another entity or group.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46ea7f0ec81908eff43aa845584af |
completed | April 19, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 9:53 a.m.