Triple
T19987767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlie |
E493976
|
entity |
| Predicate | commandMechanic |
P48192
|
FINISHED |
| Object | can throw Pikmin |
—
|
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: can throw Pikmin | Statement: [Charlie, commandMechanic, can throw Pikmin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandMechanic Context triple: [Charlie, commandMechanic, can throw Pikmin]
-
A.
featuresMechanic
chosen
Indicates that something includes or incorporates a particular mechanic as part of its design or functionality.
-
B.
driveMechanism
Indicates the mechanism or component that transmits power to drive or actuate another part of a system.
-
C.
mechanicalFunction
Indicates that one entity serves as the mechanical role, operation, or function performed by another entity or system.
-
D.
associatedWithMechanic
Indicates a relationship where an entity is connected or linked to a mechanic, such as a process, rule, or functional mechanism involved in its operation or behavior.
-
E.
interactionMechanism
Indicates the process or means by which one entity affects, influences, or interacts with another.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65fdd1a5c8190af756632aac38bf4 |
completed | April 20, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69e537fd311881908448f2aea8b4812e |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:29 p.m.