Triple
T33311232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mondoshawans |
E852881
|
entity |
| Predicate | missionOnEarth |
P179864
|
FINISHED |
| Object | secure the elemental stones |
—
|
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: secure the elemental stones | Statement: [Mondoshawans, missionOnEarth, secure the elemental stones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionOnEarth Context triple: [Mondoshawans, missionOnEarth, secure the elemental stones]
-
A.
missionTo
Indicates that one entity is assigned, directed, or sent to carry out a specific mission involving another entity or location.
-
B.
missionName
Indicates the designated title or label assigned to a specific mission or operation.
-
C.
missionPilot
Indicates that an entity serves as the pilot responsible for operating or navigating a specific mission.
-
D.
missionFirst
Indicates that one entity prioritizes accomplishing a mission or objective above other considerations or interests.
-
E.
intendedMission
Indicates that one entity is the planned or designated mission, task, or objective associated with another entity.
- F. None of above. chosen
Provenance (4 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_69f349679fd8819093b9b40e989440e3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
| PDg | Predicate description generation | batch_69f727ad9ff88190ba8069dd48b2e98f |
completed | May 3, 2026, 10:47 a.m. |
Created at: May 1, 2026, 1:33 a.m.