Triple
T19651317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T206 Honus Wagner baseball card |
E471821
|
entity |
| Predicate | setNickname |
P136833
|
FINISHED |
| Object | White Border set |
—
|
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: White Border set | Statement: [T206 Honus Wagner baseball card, setNickname, White Border set]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setNickname Context triple: [T206 Honus Wagner baseball card, setNickname, White Border set]
-
A.
changedNicknameTo
Indicates that an entity has altered another entity’s nickname to a specified new nickname.
-
B.
decidingPlayNickname
Indicates that an entity is choosing or determining a nickname to be used for a play.
-
C.
localNickname
Indicates that an entity is known by a particular nickname within a specific local or regional context.
-
D.
usedNicknameSystem
Indicates that one entity referred to another entity using a nickname rather than their formal name.
-
E.
usesNicknameOf
Indicates that one entity refers to another entity by a nickname derived from or associated with that other entity’s name.
- 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e64141f61c819098fe148581fb1747 |
completed | April 20, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e51a23300c8190988552491d9783d7 |
completed | April 19, 2026, 6:08 p.m. |
Created at: April 10, 2026, 1:44 p.m.