Triple
T6001112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wagon Wheel rivalry |
E133596
|
entity |
| Predicate | hasAlumniInterest |
P67941
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Wagon Wheel rivalry, hasAlumniInterest, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlumniInterest Context triple: [Wagon Wheel rivalry, hasAlumniInterest, high]
-
A.
hasAlumniInvolvement
Indicates that an entity maintains an ongoing relationship or engagement with its former members or graduates.
-
B.
hasAlumni
Indicates that an institution or organization is associated with individuals who formerly attended or graduated from it.
-
C.
hasAlumniNetwork
Indicates that an entity maintains or is associated with an organized network or community of its former members or graduates.
-
D.
hasAlumnusTeam
Indicates a relationship where an educational institution is associated with a sports team composed of its former students (alumni).
-
E.
hasAlumnusLeague
Indicates that an educational institution has at least one alumnus who is or was a member of a specified sports league.
- F. None of above. chosen
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_69c00872444c8190bfaf1739dcec765c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04ee7c0e08190a6e78969448b070a |
completed | March 22, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69c049e152e88190979ab80cb9b50321 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04dbefd1081909795fe1a812b991a |
completed | March 22, 2026, 8:14 p.m. |
Created at: March 22, 2026, 4:05 p.m.