Triple
T21258105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gyeongbokgung |
E523920
|
entity |
| Predicate | restorationOngoing |
P13045
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Gyeongbokgung, restorationOngoing, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restorationOngoing Context triple: [Gyeongbokgung, restorationOngoing, true]
-
A.
restorationProject
Indicates a project whose purpose is to repair, renew, or return something to a previous or improved condition.
-
B.
attemptedRestoration
Indicates an action where an entity makes an effort to restore or return another entity to a previous or desired state, condition, or form, regardless of whether the restoration succeeds.
-
C.
restorationBeganWith
Indicates that the initiation of a restoration process started with or was triggered by a specified prior event, action, or condition.
-
D.
hasRestoration
chosen
Indicates that an entity has undergone, is undergoing, or is associated with a process of repair, renewal, or restoration.
-
E.
restorationEnd
Indicates the point in time or condition at which a restoration process or restorative state comes to an end.
- 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_69e0b5146c108190adc9adb73e90abff |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735e477d08190be17ad5384d69a80 |
completed | April 21, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:58 p.m.