Triple
T3537055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Mario |
E74795
|
entity |
| Predicate | typicalCollectible |
P2370
|
FINISHED |
| Object | coins |
—
|
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: coins | Statement: [Super Mario, typicalCollectible, coins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCollectible Context triple: [Super Mario, typicalCollectible, coins]
-
A.
collectibleAspect
chosen
Indicates that one entity represents a collectible-related characteristic, feature, or dimension associated with another entity.
-
B.
collects
Indicates that one entity gathers, accumulates, or brings together one or more other entities into its possession or control.
-
C.
significantCollector
Indicates that an entity plays an important or notable role in collecting items, works, or data related to another entity.
-
D.
isTypicallySoldAs
Indicates that one entity is commonly offered for sale in the form, packaging, or configuration represented by another entity.
-
E.
coinsCollectedFor
Indicates that a certain number of coins has been gathered or accumulated in order to benefit or be used for a particular entity or purpose.
- 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_69ad85d274cc8190ab59c97298a1cfbf |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbcc7b92481908d2d99948780f4d0 |
completed | March 8, 2026, 6:15 p.m. |
| PD | Predicate disambiguation | batch_69adae13ab808190a5d6ecdc7543445e |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:20 p.m.