Triple
T4244496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Cambodia |
E95494
|
entity |
| Predicate | modernRestoration |
P8589
|
FINISHED |
| Object | 1993 |
—
|
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: 1993 | Statement: [King of Cambodia, modernRestoration, 1993]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernRestoration Context triple: [King of Cambodia, modernRestoration, 1993]
-
A.
modernRevivalIn
Indicates that something has experienced a renewed or modern resurgence, popularity, or reinterpretation within a specified place, context, or period.
-
B.
restorationProject
Indicates a project whose purpose is to repair, renew, or return something to a previous or improved condition.
-
C.
reconstructionOrRestorationDate
chosen
Indicates the date on which an entity was reconstructed or restored after damage, alteration, or deterioration.
-
D.
modernAccess
Indicates that an entity has contemporary, up-to-date means or methods of accessing or interacting with another entity or resource.
-
E.
restored
Indicates that an entity has returned another entity to a previous or improved state, condition, or position after damage, loss, or alteration.
- 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_69b3453d91548190b4d4ef8fe52aa2ac |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e8c42e88190b309a1ef7f6529ac |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f587148190a1830503459939b6 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.