Triple
T1720120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long-Term Servicing Channel |
E37369
|
entity |
| Predicate | configurationScope |
P25607
|
FINISHED |
| Object | enterprise environments |
—
|
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: enterprise environments | Statement: [Long-Term Servicing Channel, configurationScope, enterprise environments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: configurationScope Context triple: [Long-Term Servicing Channel, configurationScope, enterprise environments]
-
A.
organizationalScope
Indicates the range or extent of responsibility, authority, or applicability that an action, policy, or relationship has within an organization or its sub-units.
-
B.
locationScope
Indicates the specific geographic or spatial area within which a given relationship, condition, or action is considered valid or applicable.
-
C.
scopeType
chosen
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
-
D.
coverageScope
Indicates the extent or range of entities, conditions, or situations that are included under a particular coverage or applicability.
-
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.
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_69a8861912dc8190931af43b4b9158a7 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab5c96db6c8190a745d6fef7bf2cdb |
completed | March 6, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69aa61bed2fc819086d912cd34285978 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.