Triple
T8827737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archipelago Management Board |
E210057
|
entity |
| Predicate | decisionMakingStructure |
P35633
|
FINISHED |
| Object | consensus-based |
—
|
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: consensus-based | Statement: [Archipelago Management Board, decisionMakingStructure, consensus-based]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisionMakingStructure Context triple: [Archipelago Management Board, decisionMakingStructure, consensus-based]
-
A.
decisionMaking
Indicates the process by which an entity evaluates options and selects a course of action among alternatives.
-
B.
decisionSplit
Indicates that a single decision point branches into multiple alternative outcomes or paths.
-
C.
decisionType
Indicates the specific category or nature of a decision associated with an entity or event.
-
D.
controlStructure
Indicates a relationship where one entity governs, regulates, or directs the behavior, operation, or flow of another entity or process.
-
E.
decisionMakingRule
chosen
Indicates the principle, guideline, or procedure that governs how a decision is made in a given context.
- 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_69ca8365b28081909e48e45e95dfc405 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc604ac0288190b59344bced8ac733 |
completed | April 1, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69cc5c23d08481908d8c9b0ad3d1dc00 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:47 p.m.