Triple
T19148388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Honus Wagner |
E468740
|
entity |
| Predicate | isLegendaryIn |
P122560
|
FINISHED |
| Object | American baseball history |
—
|
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: American baseball history | Statement: [John Honus Wagner, isLegendaryIn, American baseball history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLegendaryIn Context triple: [John Honus Wagner, isLegendaryIn, American baseball history]
-
A.
isLegendaryStatus
chosen
Indicates that an entity possesses a legendary status, typically signifying exceptional rarity, renown, or significance within a given context.
-
B.
includesLegendaryCard
Indicates that an entity (such as a deck, pack, or collection) contains at least one legendary card.
-
C.
isMythical
Indicates that the entity is considered mythical, existing only in legend, folklore, or imagination rather than in reality.
-
D.
mainLegendaryPokémon
Indicates that one Pokémon serves as the primary or central legendary Pokémon associated with a particular context, such as a game, region, or storyline.
-
E.
legendaryNameFor
Indicates that one entity is known or referred to by the other entity as its legendary or mythic name.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e97b48508190b61458821b6475ad |
completed | April 20, 2026, 8:53 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b475d88190a8c15e8eb01dbfef |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.