Triple
T26325909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lan Xang |
E662250
|
entity |
| Predicate | royalReligionCenter |
P23109
|
FINISHED |
| Object | Luang Prabang |
—
|
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: Luang Prabang | Statement: [Lan Xang, royalReligionCenter, Luang Prabang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royalReligionCenter Context triple: [Lan Xang, royalReligionCenter, Luang Prabang]
-
A.
ecclesiasticalCenter
chosen
Indicates that a place functions as a primary religious or church administrative hub for a surrounding area or community.
-
B.
religiousHouse
Indicates that an entity is a religious institution or building used for worship, residence, or activities of a religious community.
-
C.
dynasticReligionRole
Indicates a relationship where an entity holds a religious office, function, or status specifically within the context of a ruling dynasty or hereditary line.
-
D.
rulerReligion
Indicates that a ruler adheres to, practices, or is officially associated with a particular religion.
-
E.
dynasticReligion
Indicates that a dynasty or ruling family is associated with, practices, or is characterized by a particular religion.
- 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_69ee812f32748190871d970c4e2a8ddf |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60f2fec2c8190a0271e3256f22be6 |
completed | May 2, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:31 p.m.