Triple
T34594605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BDFL |
E888275
|
entity |
| Predicate | governanceBenefit |
P203260
|
FINISHED |
| Object | clear final authority |
—
|
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: clear final authority | Statement: [BDFL, governanceBenefit, clear final authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governanceBenefit Context triple: [BDFL, governanceBenefit, clear final authority]
-
A.
governanceTitle
Indicates the official role or position an entity holds within a governance or leadership structure.
-
B.
governanceIncludes
Indicates that a governance structure or framework encompasses, incorporates, or has authority over the specified component, process, or entity.
-
C.
governance
Indicates the relationship in which one entity exercises authority, control, or decision-making power over the policies, actions, or direction of another entity or system.
-
D.
governanceView
Indicates a perspective, framework, or representation of how governance is structured, managed, or overseen within a given context.
-
E.
governanceCategory
Indicates the type or classification of governance under which an entity, action, or relationship is organized or regulated.
- 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_69f349d3bfcc81909874c99e646fb3ea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a0143a4ab3c8190a240b0facfe130a9 |
completed | May 11, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_6a01426b2d4481908654bfa4a02c457d |
completed | May 11, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_6a0143a400f881909599405b47dc1c78 |
completed | May 11, 2026, 2:49 a.m. |
Created at: May 1, 2026, 2:03 a.m.