Triple
T32368216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington & Jefferson Presidents football team |
E827055
|
entity |
| Predicate | locationOfCollege |
P195618
|
FINISHED |
| Object | Washington, Pennsylvania |
E153768
|
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: Washington, Pennsylvania | Statement: [Washington & Jefferson Presidents football team, locationOfCollege, Washington, Pennsylvania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfCollege Context triple: [Washington & Jefferson Presidents football team, locationOfCollege, Washington, Pennsylvania]
-
A.
collegeLocation
chosen
Indicates the geographical place where a college is situated or based.
-
B.
locatedInCollege
Indicates that an entity is situated within or belongs to a specific college.
-
C.
universityLocatedIn
Indicates that a university is situated within or associated with a specific geographic location or administrative region.
-
D.
positionOnCampus
Indicates the spatial location or placement of an entity within the boundaries or layout of a campus.
-
E.
cityCampusServes
Indicates that a city campus provides services, resources, or support to a particular population, area, or institution.
- 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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a02f847b9848190a9fedbc411ae0918 |
completed | May 12, 2026, 9:52 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a347b6b200881909cac4fe9445ee751 |
completed | June 18, 2026, 11:12 p.m. |
| PD | Predicate disambiguation | batch_6a02f556860c8190b2995433fa05fdd0 |
completed | May 12, 2026, 9:39 a.m. |
Created at: May 1, 2026, 12:50 a.m.