Triple
T22424828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jouvert |
E554340
|
entity |
| Predicate | hasOriginContext |
P18207
|
FINISHED |
| Object | post-emancipation Trinidad |
—
|
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: post-emancipation Trinidad | Statement: [Jouvert, hasOriginContext, post-emancipation Trinidad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginContext Context triple: [Jouvert, hasOriginContext, post-emancipation Trinidad]
-
A.
hasOriginIn
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
B.
hasOriginFeature
Indicates that an entity possesses a specific characteristic, attribute, or feature related to its origin or source.
-
C.
originContext
chosen
Indicates the situational or environmental circumstances from which an entity, event, or piece of information originates.
-
D.
hasLocalContext
Indicates that something exists or occurs within a specific, surrounding situational or environmental context tied to a particular place or scope.
-
E.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
- 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_69e11e4f2d0c819091aa3558ea2ee630 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15a2c47bc81908b8265d83fa6fb65 |
completed | April 29, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.