Triple
T36130430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 212th Rescue Squadron |
E1044998
|
entity |
| Predicate | dutyEnvironment |
P853
|
FINISHED |
| Object | arctic conditions |
—
|
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: arctic conditions | Statement: [212th Rescue Squadron, dutyEnvironment, arctic conditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dutyEnvironment Context triple: [212th Rescue Squadron, dutyEnvironment, arctic conditions]
-
A.
environmentType
chosen
Indicates the kind or category of environment associated with an entity or situation.
-
B.
environmentClass
Indicates that an entity belongs to, or is categorized within, a particular type or class of environment.
-
C.
builtEnvironment
Indicates that something is part of, related to, or characteristic of human-made physical surroundings such as buildings, infrastructure, and other constructed spaces.
-
D.
supportsEnvironment
Indicates that one entity provides the necessary conditions, compatibility, or resources for another entity to operate or exist within a particular environment.
-
E.
usedInEnvironment
Indicates that something is utilized or operates within a particular environment or context.
- 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_69f76e356c908190abc6ca1e6a05b011 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b3e2f3c08190be4fd1ae4fa1266d |
completed | May 3, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bcc47081909fe7d592ac69006c |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.