Triple
T11570874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kevin (Minion) |
E274381
|
entity |
| Predicate | missionInMinions |
P68
|
FINISHED |
| Object | Leads quest to find a new master |
—
|
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: Leads quest to find a new master | Statement: [Kevin (Minion), missionInMinions, Leads quest to find a new master]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionInMinions Context triple: [Kevin (Minion), missionInMinions, Leads quest to find a new master]
-
A.
intendedMission
Indicates that one entity is the planned or designated mission, task, or objective associated with another entity.
-
B.
mission
chosen
Indicates that an entity is assigned or engaged in a specific task, operation, or purpose-directed undertaking.
-
C.
missionTo
Indicates that one entity is assigned, directed, or sent to carry out a specific mission involving another entity or location.
-
D.
capturesMissionOf
Indicates that one entity records, represents, or encapsulates the mission or overarching purpose of another entity.
-
E.
publicMission
Indicates that an entity carries out a mission or activity intended for the general public or serving public interests.
- 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_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88dd6913881908becf188c0a7a275 |
completed | April 10, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69d85dc3fc2c8190bed7e2111301a77c |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:37 p.m.