Triple
T36067952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nilame |
E1043283
|
entity |
| Predicate | notableDerivativeTitle |
P154324
|
FINISHED |
| Object | Diyawadana Nilame |
E1043283
|
NE 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: Diyawadana Nilame | Statement: [Nilame, notableDerivativeTitle, Diyawadana Nilame]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDerivativeTitle Context triple: [Nilame, notableDerivativeTitle, Diyawadana Nilame]
-
A.
notableTitleType
Indicates that a title associated with an entity is of a type considered notable or especially significant.
-
B.
notableTitleOnTheLine
Indicates that a significant or prestigious title is at stake or being contested in the associated event or context.
-
C.
notableTitleReleaseYear
Indicates the year in which a notable work or title associated with an entity was released.
-
D.
notableTitleAssociation
chosen
Indicates an association where an entity is linked to a distinguished or noteworthy title, role, or honor it holds or has held.
-
E.
notableDuo
Indicates that two entities are widely recognized together as a famous or significant pair.
- F. None of above.
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_69f76e2fd3248190b900d9a492bf5a7a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38cbac88908190916312c0df9521cd |
completed | June 22, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.