Triple
T26670718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morača Monastery |
E672322
|
entity |
| Predicate | wasRebuiltInCentury |
P11509
|
FINISHED |
| Object | 16th century |
—
|
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: 16th century | Statement: [Morača Monastery, wasRebuiltInCentury, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasRebuiltInCentury Context triple: [Morača Monastery, wasRebuiltInCentury, 16th century]
-
A.
rebuiltInCentury
chosen
Indicates that an existing structure or entity was reconstructed or significantly rebuilt during a specified century.
-
B.
partiallyRebuiltInCentury
Indicates that an entity underwent partial reconstruction or significant repair during the specified century.
-
C.
wasRepopulatedInCentury
Indicates that a place or region, previously depopulated or abandoned, became populated again during the specified century.
-
D.
reestablishedInCentury
Indicates that an entity, previously established and then discontinued or disrupted, was re-founded or restored during a specified century.
-
E.
reacquiredInCentury
Indicates that an entity was reacquired during a specified century.
- 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_69eecda00a9c8190b2691f4d89db03b6 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f616ff2b4c819082cbf51410336d4a |
completed | May 2, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:12 a.m.