Triple
T6124897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbia Lions football |
E136570
|
entity |
| Predicate | nickname |
P55
|
FINISHED |
| Object | Lions |
E274376
|
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: Lions | Statement: [Columbia Lions football, nickname, Lions]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lions Context triple: [Columbia Lions football, nickname, Lions]
-
A.
Lions
The Lions are the athletic teams representing Texas A&M University–Commerce in collegiate sports.
-
B.
Lions
chosen
The Lions are the athletic teams representing Columbia University, most notably its men's basketball program competing in NCAA Division I.
-
C.
Lions
Lions is a professional ice hockey team based in Frankfurt, Germany, competing in the country’s top leagues under the name Frankfurt Lions.
-
D.
Lions
The Lions are the men's basketball team representing Loyola Marymount University in NCAA Division I competition.
-
E.
Lions
The Lions are a South African professional rugby union team based in Johannesburg that competes in major domestic and international competitions.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c0089f851c81909e5e189a617dcff6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05c2791948190ba33458edfd1ebe8 |
completed | March 22, 2026, 9:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c135b2500c8190aaf67b059ccbe3f1 |
completed | March 23, 2026, 12:44 p.m. |
Created at: March 22, 2026, 4:14 p.m.