Triple
T37458893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shielded Minibot |
E930867
|
entity |
| Predicate | playableInFormat |
P101458
|
FINISHED |
| Object | Wild |
—
|
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: Wild | Statement: [Shielded Minibot, playableInFormat, Wild]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playableInFormat Context triple: [Shielded Minibot, playableInFormat, Wild]
-
A.
hasPlayFormat
chosen
Indicates that something (such as a game, media, or activity) is associated with a particular format or mode in which it is played or experienced.
-
B.
playableWith
Indicates that one entity can be used, engaged, or interacted with together alongside another entity, typically in a compatible or cooperative manner.
-
C.
operatesInFormat
Indicates that an entity functions, performs its role, or is carried out using a specified format.
-
D.
audioFormatSupported
Indicates that a particular audio format is recognized and can be correctly processed or played by a given system or component.
-
E.
presentedInFormat
Indicates that something is expressed, delivered, or made available using a particular format or representation.
- 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.