Triple
T2221421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Castle in Warsaw |
E48148
|
entity |
| Predicate | reconstructedInPeriod |
P16794
|
FINISHED |
| Object | 1971–1984 |
—
|
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: 1971–1984 | Statement: [Royal Castle in Warsaw, reconstructedInPeriod, 1971–1984]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reconstructedInPeriod Context triple: [Royal Castle in Warsaw, reconstructedInPeriod, 1971–1984]
-
A.
reconstructedDuring
Indicates that an entity was rebuilt, restored, or significantly repaired within a specified time period or event.
-
B.
reconstructionPeriod
chosen
Indicates a time span during which something that was damaged, destroyed, or altered is being rebuilt, restored, or substantially repaired.
-
C.
reconstructedIn
Indicates that something has been rebuilt, restored, or re-created within a particular context, location, or medium.
-
D.
reconstructedAfter
Indicates that one entity has been rebuilt, restored, or reassembled following the occurrence or existence of another entity or event.
-
E.
functionDuringReconstructionEra
Indicates that an entity performs or holds a particular function, role, or activity specifically during the Reconstruction Era.
- 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_69a88aa1ee708190862c8c378c41e9eb |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc0156c8c819083e3e3b6ede1e951 |
completed | March 7, 2026, 6:05 a.m. |
| PD | Predicate disambiguation | batch_69abbdac31d8819092d17815e11921e9 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.