Triple
T26710572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dulus |
E673398
|
entity |
| Predicate | hasVernacularMemberName |
P72248
|
FINISHED |
| Object | palmchat |
—
|
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: palmchat | Statement: [Dulus, hasVernacularMemberName, palmchat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVernacularMemberName Context triple: [Dulus, hasVernacularMemberName, palmchat]
-
A.
hasNameInLocalLanguage
Indicates that an entity is associated with a name expressed in the local or native language of a given context or region.
-
B.
hasLatinizedName
Indicates that an entity is associated with a version of its name that has been converted into Latin form or spelling.
-
C.
hasEthnologueName
Indicates that an entity is associated with a specific language name as recorded in the Ethnologue reference.
-
D.
hasLocaleName
chosen
Indicates that an entity has a specific name or label used in a particular language or regional locale.
-
E.
hasEnglishName
Indicates that an entity is associated with a name expressed in the English language.
- 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_69eecda3a22881908f3061c760b9d542 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 3:35 a.m.