Triple
T16397856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LooseConfederations |
E398228
|
entity |
| Predicate | coordinationStyle |
P123264
|
FINISHED |
| Object | decentralized |
—
|
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: decentralized | Statement: [LooseConfederations, coordinationStyle, decentralized]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coordinationStyle Context triple: [LooseConfederations, coordinationStyle, decentralized]
-
A.
coordinationRule
Indicates a rule or constraint that governs how multiple entities or actions are coordinated or combined with each other.
-
B.
coordina
Indicates that one entity organizes, directs, or harmonizes the actions or efforts of another entity or group toward a common goal.
-
C.
coordinatedWith
Indicates that two or more entities have worked together in an organized, cooperative manner toward a shared task, goal, or activity.
-
D.
coordinateRoleIn
Indicates a relationship where one entity organizes, aligns, or manages the roles or responsibilities of another entity within a shared activity, structure, or context.
-
E.
positionStyle
Indicates how an entity is positioned or arranged relative to a reference frame, layout, or context.
- 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e327cc5c9c8190ba1a70f9e430cefb |
completed | April 18, 2026, 6:42 a.m. |
| PD | Predicate disambiguation | batch_69e226fe1dd08190865c181721f8c348 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:09 a.m.