Triple
T24885822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Landcrab |
E622846
|
entity |
| Predicate | involvedEnvironment |
P70999
|
FINISHED |
| Object | subarctic climate |
—
|
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: subarctic climate | Statement: [Operation Landcrab, involvedEnvironment, subarctic climate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedEnvironment Context triple: [Operation Landcrab, involvedEnvironment, subarctic climate]
-
A.
environmentType
Indicates the kind or category of environment associated with an entity or situation.
-
B.
secondaryEnvironment
Indicates that an entity is associated with an additional or supporting environment distinct from its primary one.
-
C.
involves
Indicates that an entity participates in, is a part of, or is implicated within a particular event, process, or relationship.
-
D.
engagementEnvironment
chosen
Indicates the situational context or setting in which an interaction, activity, or engagement takes place.
-
E.
environmentalFactor
Indicates that one entity functions as an environmental influence or condition that affects another entity or process.
- 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_69e2fac4aa848190b3446a3922cec150 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 18, 2026, 5:25 a.m.