Triple
T19148390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Honus Wagner |
E468740
|
entity |
| Predicate | T206CardStatus |
P134605
|
FINISHED |
| Object | one of the most valuable baseball cards |
—
|
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: one of the most valuable baseball cards | Statement: [John Honus Wagner, T206CardStatus, one of the most valuable baseball cards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: T206CardStatus Context triple: [John Honus Wagner, T206CardStatus, one of the most valuable baseball cards]
-
A.
t20IStatus
Indicates the status or classification of an entity specifically in the context of Twenty20 International (T20I) cricket.
-
B.
hasCardBack
Indicates that an entity possesses or is associated with a specific card back design or reverse side.
-
C.
statusWithCardinals
Indicates a relationship where an entity’s status or condition is defined or evaluated specifically in relation to cardinal numbers (e.g., counts, rankings, or numeric positions).
-
D.
hasNumberOfCards
Indicates that an entity is associated with a specific quantity of cards.
-
E.
cardPosition
Indicates the specific place or order a card occupies within a sequence, deck, or layout.
- 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_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. |
| PDg | Predicate description generation | batch_69e4bfe9ef7081908a74a57d1fc731ea |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:06 p.m.