Triple
T27922439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commercial Division |
E706240
|
entity |
| Predicate | caseManagementFeatures |
P163779
|
FINISHED |
| Object | specialized commercial procedures |
—
|
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: specialized commercial procedures | Statement: [Commercial Division, caseManagementFeatures, specialized commercial procedures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caseManagementFeatures Context triple: [Commercial Division, caseManagementFeatures, specialized commercial procedures]
-
A.
caseManagementFeatures
chosen
Indicates that an entity provides or is associated with tools and capabilities for managing cases, such as tracking, organizing, and resolving case-related activities.
-
B.
caseManagement
Indicates that one entity is responsible for coordinating, organizing, and overseeing services or actions provided to another entity within a managed process or case.
-
C.
usesCaseManagementSystem
Indicates that an entity makes use of a case management system to organize, track, or handle cases or workflows.
-
D.
legalSystemFeature
Indicates a characteristic, rule, or structural element that forms part of a particular legal system.
-
E.
caseRecords
Indicates that there exist documented records associated with a particular case or legal proceeding.
- 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_69ef96b6cc808190aab19fb18b235f4b |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 6:58 p.m.