Triple
T11076916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Monk (2011 film) |
E261890
|
entity |
| Predicate | religiousOrderOfProtagonist |
P20285
|
FINISHED |
| Object | Capuchin |
—
|
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: Capuchin | Statement: [The Monk (2011 film), religiousOrderOfProtagonist, Capuchin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousOrderOfProtagonist Context triple: [The Monk (2011 film), religiousOrderOfProtagonist, Capuchin]
-
A.
religiousOrderAssociation
chosen
Indicates that an entity is formally connected to, affiliated with, or a member of a particular religious order.
-
B.
founderReligiousOrder
Indicates that a person established or created a particular religious order.
-
C.
religiousOrderInfluence
Indicates that one religious order exerts influence, guidance, or control over another entity, such as a person, group, or institution.
-
D.
religiousOrderSupported
Indicates that one entity provides support—such as resources, endorsement, or maintenance—to a particular religious order.
-
E.
inspiredReligiousOrder
Indicates that one entity motivated, influenced, or served as a model for the founding or development of a particular religious order.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7999407288190a901d4a2427a2102 |
completed | April 9, 2026, 12:20 p.m. |
| PD | Predicate disambiguation | batch_69d74415403c81909778bcd829e8832e |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.