Triple
T2737057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naval Special Warfare Command |
E60653
|
entity |
| Predicate | primaryEnvironment |
P25100
|
FINISHED |
| Object | maritime |
—
|
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: maritime | Statement: [Naval Special Warfare Command, primaryEnvironment, maritime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryEnvironment Context triple: [Naval Special Warfare Command, primaryEnvironment, maritime]
-
A.
primaryEcosystem
Indicates the main type of ecosystem in which an entity predominantly exists or operates.
-
B.
dominantEnvironment
chosen
Indicates the primary or prevailing environment or setting in which an entity most characteristically exists, operates, or exerts influence.
-
C.
environmentType
Indicates the kind or category of environment associated with an entity or situation.
-
D.
environmentalMedium
Indicates the environmental context or medium (such as air, water, or soil) through which a substance, effect, or process occurs or is present.
-
E.
environmentalCondition
Indicates the state or characteristics of the surrounding physical environment that affect or describe a situation, process, or entity.
- 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_69ab4b77febc819095603eb012cd141b |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb12e03c8190b270c814ce47b626 |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd82859348190bce3be8f2e9d60ba |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.