Triple
T10000733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F117 |
E197317
|
entity |
| Predicate | applicationEnvironment |
P14668
|
FINISHED |
| Object | long-range operations |
—
|
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-range operations | Statement: [F117, applicationEnvironment, long-range operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: applicationEnvironment Context triple: [F117, applicationEnvironment, long-range operations]
-
A.
launchEnvironment
Indicates the specific context, configuration, or setting in which a launch or deployment action takes place.
-
B.
productionEnvironment
Indicates that something is part of, deployed to, or operating within a live production environment as opposed to a test or development setting.
-
C.
applicationLocation
chosen
Indicates the place or environment where an application is deployed, used, or made available.
-
D.
environmentType
Indicates the kind or category of environment associated with an entity or situation.
-
E.
appliesToOperationalEnvironment
Indicates that something (such as a rule, requirement, or condition) is relevant to, valid in, or specifically intended for a particular operational environment.
- 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_69ca82f3b61c81908ecc2c1c96dbc2e4 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdcc8f50888190b2f1c5240cb58e4f |
completed | April 2, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69cd1da2cf9081908a6c0eb5247d0bc2 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:51 p.m.