Triple
T26586309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | postcolonial Bengal |
E667217
|
entity |
| Predicate | hasArticulationIn |
P15666
|
FINISHED |
| Object | postcolonial studies |
—
|
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: postcolonial studies | Statement: [postcolonial Bengal, hasArticulationIn, postcolonial studies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArticulationIn Context triple: [postcolonial Bengal, hasArticulationIn, postcolonial studies]
-
A.
hasArticulation
chosen
Indicates that one entity possesses or exhibits a specific type or structure of articulation in relation to another entity or system.
-
B.
hasArticulationType
Indicates the specific manner or type of connection or joint by which two parts or entities are linked or articulated.
-
C.
articulationWith
Indicates a structural or functional connection where one entity forms a joint or point of movement with another.
-
D.
usesArticulators
Indicates that an entity performs an action or produces a signal by employing specific speech or movement articulators (e.g., tongue, lips, jaw).
-
E.
articulatedWith
Indicates that two parts are connected by a joint or mechanism that allows controlled movement between them.
- 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 27, 2026, 2:05 a.m.