Triple
T27494048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Lanna |
E693974
|
entity |
| Predicate | hasTitleInLocalLanguage |
P85853
|
FINISHED |
| Object | Phaya Lanna |
—
|
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: Phaya Lanna | Statement: [King of Lanna, hasTitleInLocalLanguage, Phaya Lanna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleInLocalLanguage Context triple: [King of Lanna, hasTitleInLocalLanguage, Phaya Lanna]
-
A.
hasTitleInLanguage
Indicates that an entity has a specific title expressed in a particular language.
-
B.
titleInLocalLanguage
chosen
Indicates that an entity’s title is expressed in the primary or native language of a specified place or community.
-
C.
hasTitleInEnglishOrthography
Indicates that an entity has a specific title expressed using English spelling and writing conventions.
-
D.
hasTitleInTransliteration
Indicates that an entity has a specific title represented in a transliterated form from another writing system.
-
E.
hasNameInLocalLanguage
Indicates that an entity is associated with a name expressed in the local or native language of a given context or region.
- 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_69ef5382b9648190be0b1ef2ad5d043c |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 27, 2026, 1:07 p.m.