Triple
T20191315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Captain Olimar |
E492983
|
entity |
| Predicate | goalInPikmin |
P67602
|
FINISHED |
| Object | recover ship parts of the S.S. Dolphin |
—
|
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: recover ship parts of the S.S. Dolphin | Statement: [Captain Olimar, goalInPikmin, recover ship parts of the S.S. Dolphin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalInPikmin Context triple: [Captain Olimar, goalInPikmin, recover ship parts of the S.S. Dolphin]
-
A.
goalIn
Indicates that one entity’s objective, aim, or intended outcome is located within, directed toward, or achieved inside another entity or context.
-
B.
goalType
Indicates the specific category or nature of a goal associated with an entity or action.
-
C.
machineGoal
Indicates that a machine or automated system has a specific objective, target state, or outcome it is intended or programmed to achieve.
-
D.
goalNumber
Indicates that an entity is associated with a specific target or objective quantified as a number.
-
E.
gameObjective
chosen
Indicates the primary goal or intended outcome that participants aim to achieve within a game.
- 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.