Triple
T1197386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cornell Big Red football |
E25698
|
entity |
| Predicate | playsAgainst |
P18497
|
FINISHED |
| Object | other Ivy League football teams |
—
|
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: other Ivy League football teams | Statement: [Cornell Big Red football, playsAgainst, other Ivy League football teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsAgainst Context triple: [Cornell Big Red football, playsAgainst, other Ivy League football teams]
-
A.
battleOpponent
Indicates that two entities are engaged in or designated as opponents in a battle or combat scenario.
-
B.
keyOpponents
Indicates that the subject has primary or most significant opponents identified by the object.
-
C.
facedOpponent
chosen
Indicates that one entity directly confronted or competed against another as an opponent in a contest, conflict, or challenge.
-
D.
playedWith
Indicates that one entity engaged in play or a playful activity together with another entity.
-
E.
rivalOf
Indicates a relationship in which two entities compete against or oppose each other, often seeking advantage in the same domain or objective.
- 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_69a49429f5ec8190a6a205eb0ae81e5e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd9a305c819091513394f1b67784 |
completed | March 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5d40a08190b7682d8ef8075421 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.