Triple
T6137086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UCLA–USC football rivalry |
E136859
|
entity |
| Predicate | campusDistance |
P9492
|
FINISHED |
| Object | approximately 12 miles apart |
—
|
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: approximately 12 miles apart | Statement: [UCLA–USC football rivalry, campusDistance, approximately 12 miles apart]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: campusDistance Context triple: [UCLA–USC football rivalry, campusDistance, approximately 12 miles apart]
-
A.
distanceFromCampusCenter
Indicates the measured or specified distance between a given location and the central point of the campus.
-
B.
campusProximity
Indicates that one entity is located near, adjacent to, or within a short distance of a campus associated with the other entity.
-
C.
campusDistanceBetweenRivals
chosen
Indicates the physical distance separating the campuses of two rival institutions.
-
D.
adjacentToCampusOf
Indicates that one entity is located next to or directly bordering the campus area of another entity.
-
E.
campusSize
Indicates the physical extent or scale of a campus, typically measured in area or capacity.
- 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_69c008a179388190a3b5a081bbf46d55 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05c83aefc8190b0e250e96f2b10b4 |
completed | March 22, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c055f19b0c81908be34a00ab218723 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:15 p.m.