Triple
T31687936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Jamalullail |
E808710
|
entity |
| Predicate | borderingEntityOfRealm |
P120977
|
FINISHED |
| Object | Thailand |
—
|
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: Thailand | Statement: [House of Jamalullail, borderingEntityOfRealm, Thailand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderingEntityOfRealm Context triple: [House of Jamalullail, borderingEntityOfRealm, Thailand]
-
A.
borderingEntityCountry
Indicates that one country shares a land or maritime boundary with another country.
-
B.
borderingAdministrativeTerritorialEntity
chosen
Indicates that one administrative territorial entity shares a common boundary with another administrative territorial entity.
-
C.
borderingAuthorityOf
Indicates that one authority’s jurisdiction directly touches or shares a boundary with another authority’s jurisdiction.
-
D.
borderingPoliticalEntityType
Indicates that one political entity is adjacent to and shares a boundary with another political entity of a specified type.
-
E.
hasBorderWithNonSovereignEntity
Indicates that one entity shares a land or maritime border with a political or territorial unit that is not fully sovereign.
- 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_69f348ddcbc48190950cabcc25ff29b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fecb4d02f881909a9ee97ce98000d5 |
completed | May 9, 2026, 5:51 a.m. |
| PD | Predicate disambiguation | batch_69fec9846c1c8190b317f0711f0755db |
completed | May 9, 2026, 5:43 a.m. |
Created at: April 30, 2026, 11:07 p.m.