Triple
T26550394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arena Chapel |
E671662
|
entity |
| Predicate | frescoExecutionEnd |
P161032
|
FINISHED |
| Object | circa 1305 |
—
|
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: circa 1305 | Statement: [Arena Chapel, frescoExecutionEnd, circa 1305]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frescoExecutionEnd Context triple: [Arena Chapel, frescoExecutionEnd, circa 1305]
-
A.
restorationEnd
Indicates the point in time or condition at which a restoration process or restorative state comes to an end.
-
B.
representationEnded
Indicates that a previously ongoing representation or acting-on-behalf-of relationship between entities has come to an end.
-
C.
lastProcessingEnded
Indicates that the most recent processing activity or operation for the entity has come to an end.
-
D.
functionEnd
Indicates the point or condition at which a function, process, or operation terminates or completes.
-
E.
functionEndReason
Indicates the reason or cause for which a function, process, or activity comes to an end or is terminated.
- F. None of above. chosen
Provenance (4 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_69eeb32163f08190af5f81282738e27a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f614391e4c81908b14843830640ad1 |
completed | May 2, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f60f24ed608190bffe6c6084fc2f7a |
completed | May 2, 2026, 2:50 p.m. |
Created at: April 27, 2026, 1:47 a.m.