Triple
T22743190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arch Madness |
E562471
|
entity |
| Predicate | hasNicknamedRound |
P149573
|
FINISHED |
| Object | Championship game |
—
|
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: Championship game | Statement: [Arch Madness, hasNicknamedRound, Championship game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNicknamedRound Context triple: [Arch Madness, hasNicknamedRound, Championship game]
-
A.
hasNicknames
Indicates that an entity is known or referred to by one or more alternative informal names.
-
B.
notableGameNickname
Indicates that an entity is a well-known or commonly used nickname for a particular game.
-
C.
nicknamedFor
Indicates that one entity serves as the source, inspiration, or reason for another entity’s nickname.
-
D.
hasNicknamedEntityType
Indicates that an entity is associated with another entity type specifically in the role of being its nickname or informal name.
-
E.
runnerUpNickname
Indicates that one entity is the nickname used for the runner-up position or second-place finisher in relation to another entity.
- 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_69e245513a5c81908d5cb471b4fc429d |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17974c3208190ae1d6b05639cc942 |
completed | April 29, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:23 p.m.