Triple
T18042299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OISC |
E431679
|
entity |
| Predicate | hasRegimeType |
P49415
|
FINISHED |
| Object | statutory regulation |
—
|
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: statutory regulation | Statement: [OISC, hasRegimeType, statutory regulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegimeType Context triple: [OISC, hasRegimeType, statutory regulation]
-
A.
regimeType
chosen
Indicates the form or system of governance under which an entity (such as a state or organization) is ruled or administered.
-
B.
usedByRegimeType
Indicates that something (such as a method, policy, or tool) is employed or implemented by a particular type of political regime.
-
C.
hasPlayType
Indicates the type or category of play associated with an event, action, or performance.
-
D.
hasRegistrationType
Indicates that an entity is associated with a specific category or type of registration it holds or requires.
-
E.
hasRhythmicStyle
Indicates that one entity exhibits or is characterized by a particular rhythmic pattern or style in its expression or behavior.
- 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4bfef454c8190ad3787502f2bdd34 |
completed | April 19, 2026, 11:43 a.m. |
| PD | Predicate disambiguation | batch_69e3f908da508190a088aa837ea5b7af |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:25 a.m.