Triple
T36696368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Choma |
E906100
|
entity |
| Predicate | hasFullWorkTitleContext |
P112236
|
FINISHED |
| Object | Chomana Dudi |
—
|
NE NERFINISHED |
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: Chomana Dudi | Statement: [Choma, hasFullWorkTitleContext, Chomana Dudi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFullWorkTitleContext Context triple: [Choma, hasFullWorkTitleContext, Chomana Dudi]
-
A.
hasWorkTitleElement
Indicates that an entity includes a specific textual component representing a work’s title or part of a work’s title.
-
B.
hasTitleWork
chosen
Indicates that an entity is associated with a specific work by its title (i.e., the entity has or bears that work’s title).
-
C.
hasWorkingTitle
Indicates that an entity is associated with a provisional or temporary title used during its development or production.
-
D.
hasWorkTitlePattern
Indicates that an entity’s work title follows or matches a specified pattern or structured format.
-
E.
hasWorkTitleVariant
Indicates that an entity has an alternative or variant form of its work title, such as a different wording, spelling, or language version of the same title.
- 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_69f76e70d2448190bdd3ce781ba971c5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.