Triple
T16717963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OPIC |
E406271
|
entity |
| Predicate | proceduralCharacter |
P124353
|
FINISHED |
| Object | complaints mechanism |
—
|
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: complaints mechanism | Statement: [OPIC, proceduralCharacter, complaints mechanism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proceduralCharacter Context triple: [OPIC, proceduralCharacter, complaints mechanism]
-
A.
proceduralStyle
Indicates that one entity employs or is characterized by a particular procedural style associated with another entity.
-
B.
dynamicCharacter
Indicates that a character undergoes significant internal change or development over the course of a narrative.
-
C.
animatedCharacter
Indicates that an entity is a fictional character depicted through animation rather than live action.
-
D.
proceduralPosture
Indicates the current stage or status of a legal case within the judicial or administrative process at the time it is being considered or described.
-
E.
characterDesigner
Indicates a relationship where an entity is responsible for designing or creating the visual or conceptual characteristics of a character.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3865799848190af919dccde958ee4 |
completed | April 18, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326b9e84881909a9166e65bd850d6 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:20 a.m.