Triple
T5343889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | APEC fora |
E124004
|
entity |
| Predicate | usesDecisionMakingMode |
P11181
|
FINISHED |
| Object | consensus |
—
|
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 | Statement: [APEC fora, usesDecisionMakingMode, consensus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDecisionMakingMode Context triple: [APEC fora, usesDecisionMakingMode, consensus]
-
A.
makesDecisionBy
Indicates that one entity determines or chooses an outcome, course of action, or judgment by means of another entity, method, or process.
-
B.
usesDecisionBoundaryType
Indicates that one entity applies or relies on a specific type of decision boundary in making classifications or decisions.
-
C.
decisionType
Indicates the specific category or nature of a decision associated with an entity or event.
-
D.
decisionMaking
Indicates the process by which an entity evaluates options and selects a course of action among alternatives.
-
E.
decisionsAre
chosen
Indicates that certain choices, judgments, or resolutions possess a specified quality, status, or classification.
- 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_69bd464be27081908807b40b75c1bbae |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85e86edc81908d87933db6489f91 |
completed | March 20, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69bd845a62b081909782863865b257a9 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:01 p.m.