Triple
T6984420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cassino |
E161926
|
entity |
| Predicate | wasRebuiltInPeriod |
P24909
|
FINISHED |
| Object | post-World War II era |
—
|
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: post-World War II era | Statement: [Cassino, wasRebuiltInPeriod, post-World War II era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasRebuiltInPeriod Context triple: [Cassino, wasRebuiltInPeriod, post-World War II era]
-
A.
hasRebuiltDate
Indicates the date on which something was rebuilt or reconstructed.
-
B.
rebuiltOn
Indicates that one entity has been reconstructed, restored, or built again on, over, or using the foundation, structure, or basis of another entity.
-
C.
hasRebuilt
Indicates that an entity has restored, reconstructed, or built again something that previously existed or was damaged or destroyed.
-
D.
reconstructedDuring
chosen
Indicates that an entity was rebuilt, restored, or significantly repaired within a specified time period or event.
-
E.
rebuiltCompletedIn
Indicates that an entity has undergone a rebuilding process that was fully completed in a specified time or event.
- 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_69c68855dc0481909b4c7e9e9ed273db |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dbbd926c8190a8b60527bd553fa3 |
completed | March 27, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c4a18881908d267137daed828b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:31 p.m.