Triple
T24523118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darlac Province |
E606588
|
entity |
| Predicate | usedNameVariant |
P20733
|
FINISHED |
| Object | Đắk Lắk |
E560367
|
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: Đắk Lắk | Statement: [Darlac Province, usedNameVariant, Đắk Lắk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedNameVariant Context triple: [Darlac Province, usedNameVariant, Đắk Lắk]
-
A.
surnameVariant
Indicates that one surname is an alternative spelling, form, or variation of another surname.
-
B.
usesNameDueTo
Indicates that one entity adopts or applies a particular name for another entity specifically because of some motivating reason, circumstance, or dependency.
-
C.
usesNameForm
Indicates that one entity adopts or applies a particular standardized form or variant of a name associated with another entity.
-
D.
hasOfficialNameVariant
chosen
Indicates that an entity has an alternative official form or version of its name.
-
E.
isSometimesUsedAsVariantOf
Indicates that one entity is occasionally employed as an alternative or substitute form of another entity, but not as its primary or standard version.
- 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_69e2c4c85778819085f5da9af3569ad5 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a101bdfc74c8190981c550c6921c184 |
completed | May 22, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b0ca8081908d931aec560eae56 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:25 a.m.