Triple
T20191444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shepherd |
E492986
|
entity |
| Predicate | commandAbility |
P85648
|
FINISHED |
| Object | direct Pikmin in combat |
—
|
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: direct Pikmin in combat | Statement: [Shepherd, commandAbility, direct Pikmin in combat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandAbility Context triple: [Shepherd, commandAbility, direct Pikmin in combat]
-
A.
forceAbility
Indicates that one entity has the power or capacity to compel, influence, or cause another entity to act or change in a particular way.
-
B.
commandOf
Indicates that one entity holds authoritative control or leadership over another, typically in a military, organizational, or hierarchical context.
-
C.
commandedBy
Indicates that one entity holds authoritative control or issues orders over another entity.
-
D.
symbolicAbility
Indicates the capacity of an entity to understand, manipulate, or use symbols to represent concepts, objects, or relationships.
-
E.
hasProtagonistAbility
chosen
Indicates that a protagonist possesses a specific ability, power, or special skill.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ad593f88190a1e534fed38b3cd7 |
completed | April 20, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e55b11124c8190babacf2a0fe2d057 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:37 p.m.