Triple
T36826172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maud Arctic expedition |
E910015
|
entity |
| Predicate | aimedMethod |
P859
|
FINISHED |
| Object | long-term drift in sea ice |
—
|
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: long-term drift in sea ice | Statement: [Maud Arctic expedition, aimedMethod, long-term drift in sea ice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimedMethod Context triple: [Maud Arctic expedition, aimedMethod, long-term drift in sea ice]
-
A.
aimingMethod
Indicates the technique or approach used to direct or aim an action, object, or effect toward a target.
-
B.
method
chosen
Indicates the technique, procedure, or process used by an entity to perform an action or achieve a result.
-
C.
aimOf
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
D.
plannedMethod
Indicates that a particular method or procedure has been selected or designated in advance as the intended way to carry out an action or achieve a goal.
-
E.
aimedAtBy
Indicates that one entity serves as the target or goal toward which another entity directs an action, intention, or focus.
- 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_69f76e7dd13c81908c60b05adb49eeb5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7ca9c9ef88190b71bcc6f5b4a6182 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c89b528c8190bf80b230fc7c7108 |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:13 p.m.