Triple
T9849878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Door |
E239437
|
entity |
| Predicate | sealingMethod |
P40777
|
FINISHED |
| Object | 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: masonry | Statement: [Holy Door, sealingMethod, masonry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sealingMethod Context triple: [Holy Door, sealingMethod, masonry]
-
A.
sealingMechanism
Indicates a relationship where one entity functions as or provides the means by which another entity is sealed or made airtight/watertight.
-
B.
sealType
chosen
Indicates the specific kind or category of seal associated with an entity or connection.
-
C.
sealingDefinition
Indicates that one entity formally establishes or specifies the terms, conditions, or parameters under which a sealing or closure process is to occur.
-
D.
sealedBy
Indicates that one entity is closed, secured, or made airtight/watertight through the action or presence of another entity.
-
E.
isSealed
Indicates that an entity is closed off or secured so that nothing can enter, exit, or be altered.
- 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_69ca84e4fdc08190a624425bcef98665 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb372efc88190a801b2d7384445d7 |
completed | April 2, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69cd03e57cac8190914bb5ae608a6e0e |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:34 p.m.