Triple
T11456550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltit Fort |
E271541
|
entity |
| Predicate | restorationCompletedIn |
P49985
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [Baltit Fort, restorationCompletedIn, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restorationCompletedIn Context triple: [Baltit Fort, restorationCompletedIn, 1990s]
-
A.
restorationEnd
chosen
Indicates the point in time or condition at which a restoration process or restorative state comes to an end.
-
B.
wasRestoredAt
Indicates that an entity was brought back to a previous or improved state at a specific time or place.
-
C.
rebuiltCompletedIn
Indicates that an entity has undergone a rebuilding process that was fully completed in a specified time or event.
-
D.
reconstructionEndDate
Indicates the date on which a reconstruction process or project is completed.
-
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_69d6aadff8888190a13f253f0d460874 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d822f2138081909408c7916cef99c9 |
completed | April 9, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69d80867ff248190bb157fa9e355353b |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:35 p.m.