Triple
T34892153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milton Security |
E1006313
|
entity |
| Predicate | operationalEthos |
P203037
|
FINISHED |
| Object | pragmatic |
—
|
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: pragmatic | Statement: [Milton Security, operationalEthos, pragmatic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalEthos Context triple: [Milton Security, operationalEthos, pragmatic]
-
A.
operationalNature
Indicates the functional or practical manner in which an entity, process, or system operates or carries out its activities.
-
B.
operationalConcept
Indicates that one entity defines, specifies, or embodies the operational concept or way of functioning for another entity.
-
C.
operationalService
Indicates that one entity provides, performs, or is responsible for carrying out a particular service or operation for another entity.
-
D.
operationalAssessment
Indicates an evaluation of how effectively and efficiently an entity, system, or process is functioning in practice.
-
E.
operationalScope
Indicates the range, extent, or boundaries within which an entity, process, or activity is authorized or designed to operate.
- F. None of above. chosen
Provenance (4 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_69f76dbfe5788190ad8b64f241f470c8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0117b6539c8190be7d231e891fe546 |
completed | May 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_6a011762f7ec8190afc884b92419d33f |
completed | May 10, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_6a0117b4eec88190a761ac126f5cc8e2 |
completed | May 10, 2026, 11:41 p.m. |
Created at: May 3, 2026, 4 p.m.