Triple
T37459304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toshley |
E930877
|
entity |
| Predicate | generatesCardSubtype |
P100023
|
FINISHED |
| Object | Spare Part |
—
|
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: Spare Part | Statement: [Toshley, generatesCardSubtype, Spare Part]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: generatesCardSubtype Context triple: [Toshley, generatesCardSubtype, Spare Part]
-
A.
includesCardSubtype
Indicates that one entity’s set of card subtypes contains or encompasses the card subtype of another entity.
-
B.
typeOfCardinal
Indicates a classification relationship where one entity is a specific kind or subtype of a broader cardinal category represented by the other entity.
-
C.
cardSetType
Indicates the classification relationship that specifies what type or category a given card set belongs to.
-
D.
addsCardType
chosen
Indicates that one entity introduces or associates a specific card type with another entity or collection.
-
E.
createdCardinalBy
Indicates that something was brought into existence or produced through the actions or authority of a cardinal.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.