Triple
T14984074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cabinet of Barbados |
E373654
|
entity |
| Predicate | previouslyAdvised |
P116943
|
FINISHED |
| Object | monarch of Barbados |
—
|
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: monarch of Barbados | Statement: [Cabinet of Barbados, previouslyAdvised, monarch of Barbados]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previouslyAdvised Context triple: [Cabinet of Barbados, previouslyAdvised, monarch of Barbados]
-
A.
previouslyAdmitted
Indicates that an entity has already been admitted or accepted at an earlier time prior to the current reference point.
-
B.
previouslyCovered
Indicates that the subject has already been addressed, discussed, or dealt with at an earlier time or in a prior context.
-
C.
previouslyEstablished
Indicates that the relationship or condition it connects has already been formed or confirmed at an earlier time before the current context.
-
D.
previouslyAllowed
Indicates that an action or relationship was permitted at some earlier time, though it may not be allowed now.
-
E.
previouslyIssued
Indicates that something was issued or released at an earlier time prior to the current reference point.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6ff4a7c8190ab7554f3a1a09b67 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a4d8dc8190a4c0841c20f2875f |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:52 a.m.