Triple
T33498542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Festen |
E857926
|
entity |
| Predicate | followsDogme95VowOfChastity |
P27401
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Festen, followsDogme95VowOfChastity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsDogme95VowOfChastity Context triple: [Festen, followsDogme95VowOfChastity, true]
-
A.
vowedVirtue
Indicates that an entity has formally promised or committed to uphold a particular virtue or moral quality.
-
B.
vowedCelibacyWith
Indicates a mutual commitment between entities to abstain from sexual or romantic relationships, typically formalized as a shared vow of celibacy.
-
C.
isDefinedAsDogmaBy
Indicates that one entity formally establishes or declares another entity as dogma or authoritative doctrine.
-
D.
followsDoctrine
chosen
Indicates that one entity adheres to, complies with, or acts in accordance with a specified doctrine or set of guiding principles.
-
E.
takesVowsOf
Indicates that an entity formally commits to specific vows, promises, or oaths, typically within a religious, ceremonial, or institutional 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_69f3497660508190a541826a81f7e9ab |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe7bfc94bc81909eeec946e8c1c450 |
completed | May 9, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69fe7b74a1188190886f128e07f712da |
completed | May 9, 2026, 12:10 a.m. |
Created at: May 1, 2026, 1:38 a.m.