Triple
T19651343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T206 Honus Wagner baseball card |
E471821
|
entity |
| Predicate | firstMajorRecordPriceEra |
P39608
|
FINISHED |
| Object | 1980s |
—
|
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: 1980s | Statement: [T206 Honus Wagner baseball card, firstMajorRecordPriceEra, 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMajorRecordPriceEra Context triple: [T206 Honus Wagner baseball card, firstMajorRecordPriceEra, 1980s]
-
A.
firstPerformanceEra
Indicates the time period during which an entity’s earliest known performance or debut took place.
-
B.
firstMajorRunYear
Indicates the year in which something (such as an event, production, or operation) first began its major or primary run.
-
C.
firstMajorUseYear
Indicates the calendar year in which something was first put into major or primary use.
-
D.
firstMajorInstrumentallyRecordedEvent
Indicates that the event is the first major occurrence to be captured or documented through instrumental (e.g., scientific or technical) recording methods.
-
E.
notableEraStart
chosen
Indicates the point in time when a notable or historically significant era associated with an entity begins.
- 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_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. |
Created at: April 10, 2026, 1:44 p.m.