Triple
T23388344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dedication of the Archbasilica of the Most Holy Savior |
E593944
|
entity |
| Predicate | fixedOrMoveable |
P152061
|
FINISHED |
| Object | fixed feast |
—
|
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: fixed feast | Statement: [Dedication of the Archbasilica of the Most Holy Savior, fixedOrMoveable, fixed feast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fixedOrMoveable Context triple: [Dedication of the Archbasilica of the Most Holy Savior, fixedOrMoveable, fixed feast]
-
A.
movable
Indicates that an entity is capable of being moved or repositioned from one location to another.
-
B.
isFixedInstallation
Indicates that something is permanently installed or affixed in a specific location and not intended to be moved.
-
C.
fixedBy
Indicates that one entity is repaired, corrected, or resolved through the action or intervention of another entity.
-
D.
plateFixedTo
Indicates that one object is securely attached to a plate so that they remain fixed together in position.
-
E.
isFreeStanding
Indicates that an object or structure stands independently without needing external support or attachment.
- 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_69e25d2754fc819085deea939bde60ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a499bad88190afca1afb2e3fddb0 |
completed | April 29, 2026, 6:26 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:35 p.m.