Triple
T20815750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zirc |
E512431
|
entity |
| Predicate | hasRebuiltPeriod |
P44073
|
FINISHED |
| Object | 18th 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: 18th century | Statement: [Zirc, hasRebuiltPeriod, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRebuiltPeriod Context triple: [Zirc, hasRebuiltPeriod, 18th century]
-
A.
hasRebuilt
Indicates that an entity has restored, reconstructed, or built again something that previously existed or was damaged or destroyed.
-
B.
hasRebuiltDate
Indicates the date on which something was rebuilt or reconstructed.
-
C.
rebuildPeriod
chosen
Indicates the time span during which something is reconstructed or restored after damage, failure, or decommissioning.
-
D.
rebuiltBetween
Indicates that an entity was reconstructed or rebuilt during a time interval bounded by two specified temporal points.
-
E.
hasBuildingPeriod
Indicates that a building or structure is associated with a specific time period during which it was constructed or significantly developed.
- 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_69e0b4cd25088190b48ca9700cd24efc |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2d5a514819093d1a18626de8857 |
completed | April 21, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:41 p.m.