Triple
T376816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Temple in Jerusalem |
E8389
|
entity |
| Predicate | renovationBegan |
P3322
|
FINISHED |
| Object | late 1st century BCE |
—
|
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: late 1st century BCE | Statement: [Second Temple in Jerusalem, renovationBegan, late 1st century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: renovationBegan Context triple: [Second Temple in Jerusalem, renovationBegan, late 1st century BCE]
-
A.
hasRenovation
chosen
Indicates that an entity has undergone, is undergoing, or is associated with a renovation process or renovation event.
-
B.
renovationCompleted
Indicates that a renovation process for an entity has been fully finished and is no longer in progress.
-
C.
renovatedBy
Indicates that an entity has been improved, restored, or updated through renovation work performed by another entity.
-
D.
renovationFeature
Indicates that an entity has a specific renovation-related characteristic, element, or improvement associated with it.
-
E.
constructionResumed
Indicates that previously halted construction activity on an entity or project has started again.
- 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_69a2e7f2ec648190b42bc7db424f8109 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec169a848190a577aa093c878839 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e96351cc8190a55adf95f8c27e9e |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.