Triple
T10433724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Door of Humility |
E245981
|
entity |
| Predicate | requiresPosture |
P25861
|
FINISHED |
| Object | bowing |
—
|
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: bowing | Statement: [Door of Humility, requiresPosture, bowing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresPosture Context triple: [Door of Humility, requiresPosture, bowing]
-
A.
describesPosture
Indicates that one entity specifies or characterizes the bodily position or stance (posture) of another entity.
-
B.
proceduralPosture
Indicates the current stage or status of a legal case within the judicial or administrative process at the time it is being considered or described.
-
C.
hasLiturgicalPosture
chosen
Indicates that an entity is associated with a specific bodily posture or position used in a liturgical or religious ritual context.
-
D.
hasSeatingPose
Indicates that an entity is in a seated posture or arrangement, specifying how it is positioned while sitting.
-
E.
showsPose
Indicates that one entity displays or presents a particular pose or bodily posture of another entity.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea65afe08190b91260c9267a0f14 |
completed | April 7, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_69d4dfbc546881908f312c66ee195f79 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:14 p.m.