Triple
T22961685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ponte Santa Trinita |
E570915
|
entity |
| Predicate | reconstructionUsedOriginalStones |
P109932
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Ponte Santa Trinita, reconstructionUsedOriginalStones, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reconstructionUsedOriginalStones Context triple: [Ponte Santa Trinita, reconstructionUsedOriginalStones, true]
-
A.
usesOriginalStones
Indicates that something is constructed or preserved using the same stones that were part of the original structure or artifact.
-
B.
reconstructionUsedOriginalFragments
chosen
Indicates that a reconstruction was created using fragments from the original object or structure.
-
C.
rebuiltInStone
Indicates that a previously existing structure was reconstructed using stone as the primary building material.
-
D.
reconstructionUsedOriginalMaterials
Indicates that a reconstruction was carried out using the same physical materials as those of the original object or structure.
-
E.
hasReconstructionMaterial
Indicates that something is associated with, composed of, or utilizes a particular material for its reconstruction.
- 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_69e245b212a88190b5259caf51606084 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181f494348190a24f09d3495b0950 |
completed | April 29, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9101f48190a06c69dff26c6441 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:47 p.m.