Triple
T4434363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franciscan Complex |
E95610
|
entity |
| Predicate | deformation |
P35342
|
FINISHED |
| Object | intensely deformed |
—
|
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: intensely deformed | Statement: [Franciscan Complex, deformation, intensely deformed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deformation Context triple: [Franciscan Complex, deformation, intensely deformed]
-
A.
deformationFeatures
chosen
Indicates the presence or characteristics of structural changes or distortions (such as folds, faults, or warps) affecting an object or material.
-
B.
deformationStyle
Indicates the manner or pattern in which an object or material is deformed under applied forces or conditions.
-
C.
hasInternalDeformation
Indicates that one entity exhibits structural distortion or change within its interior caused by stress, force, or other internal factors.
-
D.
shape
Indicates that one entity has a particular geometric or physical form characterized by the other entity.
-
E.
shaped
Indicates that one entity has given form, contour, or structure to another entity or outcome.
- 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_69b3453ea2b48190a26f154b3b8fece5 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35588e99881908fea7b71a33e2bb6 |
completed | March 13, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69b34f6078cc8190831b89f404198cc5 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:31 p.m.