Triple
T25453614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dhives Akuru |
E637853
|
entity |
| Predicate | replacedInLanguageBy |
P29646
|
FINISHED |
| Object | Thaana in Dhivehi |
—
|
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: Thaana in Dhivehi | Statement: [Dhives Akuru, replacedInLanguageBy, Thaana in Dhivehi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedInLanguageBy Context triple: [Dhives Akuru, replacedInLanguageBy, Thaana in Dhivehi]
-
A.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
B.
replacedInCountry
Indicates that one entity has been substituted or superseded by another within the context or jurisdiction of a specific country.
-
C.
replacedWith
chosen
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
-
D.
primaryReplacementLanguage
Indicates that one language serves as the main or preferred substitute for another language when the original cannot be used.
-
E.
replacedOnPlatformBy
Indicates that one entity has been superseded or taken over by another entity on a particular platform.
- 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_69e75db7c5048190b8da9cd7eeedb610 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 21, 2026, 2:03 p.m.