Triple
T35642597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thonburi Palace |
E1029911
|
entity |
| Predicate | successorPalace |
P201818
|
FINISHED |
| Object | Grand Palace |
—
|
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: Grand Palace | Statement: [Thonburi Palace, successorPalace, Grand Palace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorPalace Context triple: [Thonburi Palace, successorPalace, Grand Palace]
-
A.
successorRealm
Indicates that one realm directly follows and replaces another in a sequence of realms or domains.
-
B.
successorInExile
Indicates that one entity is the designated or recognized successor to another while both are in exile or outside their rightful domain.
-
C.
successorAsRegent
Indicates that one entity assumes the role of regent following another, serving as their successor in that governing capacity.
-
D.
successorAsQueen
Indicates that one entity became queen directly after another, inheriting the queenship as her successor.
-
E.
successorAsPrince
Indicates that one individual directly follows another in holding the title or role of prince.
- F. None of above. chosen
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_69f76e087bdc8190a4794bf9c0bd7634 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00262d71488190a769783fb09e5803 |
completed | May 10, 2026, 6:31 a.m. |
| PD | Predicate disambiguation | batch_6a0023985f148190a335a3fb93e9981e |
completed | May 10, 2026, 6:20 a.m. |
| PDg | Predicate description generation | batch_6a00262cc9408190b95076a2d3da057d |
completed | May 10, 2026, 6:31 a.m. |
Created at: May 3, 2026, 4:05 p.m.