Triple
T4684481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaziantep Castle |
E103885
|
entity |
| Predicate | underRestoration |
P13045
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Gaziantep Castle, underRestoration, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underRestoration Context triple: [Gaziantep Castle, underRestoration, yes]
-
A.
hasRestoration
chosen
Indicates that an entity has undergone, is undergoing, or is associated with a process of repair, renewal, or restoration.
-
B.
restored
Indicates that an entity has returned another entity to a previous or improved state, condition, or position after damage, loss, or alteration.
-
C.
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.
-
D.
restoredInPart
Indicates that something has been brought back to a previous or improved state, but only partially rather than fully.
-
E.
partiallyRestored
Indicates that an entity has been brought back toward a previous or original state, but the restoration is incomplete or only partially achieved.
- 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_69bd43debbf08190b4bc372e286ec234 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd67c9c3c08190a6c4944cdd1362a8 |
completed | March 20, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69bd6217e0088190836570522e324dc6 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:16 p.m.