Triple
T24487748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calvari steps |
E617556
|
entity |
| Predicate | hasApproximateConstructionType |
P38699
|
FINISHED |
| Object | stone masonry |
—
|
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: stone masonry | Statement: [Calvari steps, hasApproximateConstructionType, stone masonry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateConstructionType Context triple: [Calvari steps, hasApproximateConstructionType, stone masonry]
-
A.
hasApproximateType
Indicates that an entity is associated with a type that is similar or close to, but not exactly, a specified type.
-
B.
hasConstruction
chosen
Indicates that one entity possesses, contains, or is characterized by a particular construction, structure, or built form associated with it.
-
C.
hasReconstructionType
Indicates the specific method or category of reconstruction applied to an object, structure, or dataset.
-
D.
hasApproximateShape
Indicates that one entity has a shape that is similar to, but not exactly the same as, the shape of another entity.
-
E.
approximationType
Indicates the specific method or scheme used to approximate a value, function, or relationship in a given context.
- 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_69e2d7f4e6bc8190aec540ae3b9ed7f2 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:22 a.m.