Triple
T26550393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arena Chapel |
E671662
|
entity |
| Predicate | frescoExecutionStart |
P118962
|
FINISHED |
| Object | circa 1303 |
—
|
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 1303 | Statement: [Arena Chapel, frescoExecutionStart, circa 1303]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frescoExecutionStart Context triple: [Arena Chapel, frescoExecutionStart, circa 1303]
-
A.
restorationBeganWith
Indicates that the initiation of a restoration process started with or was triggered by a specified prior event, action, or condition.
-
B.
productionStartApproximate
chosen
Indicates that the start of production for something is known only approximately rather than as an exact date or time.
-
C.
preparationBegan
Indicates that the initial actions or processes required for something to be carried out or occur have started.
-
D.
preservationOperationsBegan
Indicates that actions or processes aimed at preserving or safeguarding something have been initiated.
-
E.
exportStart
Indicates the point in time or event at which an export process or outbound transfer of goods, data, or resources begins.
- 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_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_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:47 a.m.