Triple
T3588018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivy League men's lacrosse |
E75956
|
entity |
| Predicate | championDetermination |
P29352
|
FINISHED |
| Object | best conference record |
—
|
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: best conference record | Statement: [Ivy League men's lacrosse, championDetermination, best conference record]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: championDetermination Context triple: [Ivy League men's lacrosse, championDetermination, best conference record]
-
A.
determinesChampionBy
chosen
Indicates that one entity establishes or decides which entity is the champion, typically as the outcome of a competition or evaluation.
-
B.
champion
Indicates that one entity has won a competition or contest and holds the top position or title over others.
-
C.
championedBy
Indicates that an entity is actively supported, promoted, or advocated for by another entity.
-
D.
conferenceOfChampion
Indicates a relationship where a conference or event is held to recognize, feature, or determine a champion.
-
E.
championManager
Indicates that one entity serves as the manager, coach, or primary overseer responsible for the success or performance of a champion entity.
- 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_69ad85d6dc3c8190b491b79b83e25461 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc13a11608190a23d76efc1b50e3c |
completed | March 8, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69adb839b4e08190b1c0d611cccb11ae |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:22 p.m.