Triple
T25587851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Sisowath Monivong |
E641435
|
entity |
| Predicate | succeededOn |
P169523
|
FINISHED |
| Object | 1927-08-07 |
—
|
LITERAL FINISHED |
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: 1927-08-07 | Statement: [King Sisowath Monivong, succeededOn, 1927-08-07]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: succeededOn Context triple: [King Sisowath Monivong, succeededOn, 1927-08-07]
-
A.
succeededUnder
Indicates that one entity achieved success or attained a position while operating under the authority, leadership, or conditions established by another entity.
-
B.
succeededByName
Indicates that one entity is followed or replaced by another entity identified by a specific name.
-
C.
achievedOn
Indicates that a particular result, milestone, or state was successfully reached or completed at a specific time or date.
-
D.
succeededByEvent
Indicates that one event directly follows and replaces another in a temporal or sequential order.
-
E.
succeedsBy
Indicates that one entity comes after or replaces another in a sequence, order, or position.
- 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f67fc237608190b6542b56038a7fe4 |
completed | May 2, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f0353c88190a05b2db449abe0f4 |
completed | May 2, 2026, 10:47 p.m. |
Created at: April 21, 2026, 4:17 p.m.