Triple
T18296098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A9X |
E438233
|
entity |
| Predicate | collectabilityReason |
P126733
|
FINISHED |
| Object | motorsport success |
—
|
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: motorsport success | Statement: [A9X, collectabilityReason, motorsport success]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectabilityReason Context triple: [A9X, collectabilityReason, motorsport success]
-
A.
collectibleFor
Indicates that one entity is intended or suitable to be collected by, or kept as part of a collection for, another entity.
-
B.
collectibleIn
Indicates that one entity can be collected or obtained within the context, location, or container defined by another entity.
-
C.
collectibleAspect
Indicates that one entity represents a collectible-related characteristic, feature, or dimension associated with another entity.
-
D.
rarityReason
chosen
Indicates the underlying cause or justification for why something is considered rare.
-
E.
collects
Indicates that one entity gathers, accumulates, or brings together one or more other entities into its possession or control.
- 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5017c0f04819095cd9d59afc37caa |
completed | April 19, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:35 a.m.