Triple
T34781631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church Without Christ |
E1002678
|
entity |
| Predicate | usedAsDevice |
P196801
|
FINISHED |
| Object | satirical device |
—
|
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: satirical device | Statement: [Church Without Christ, usedAsDevice, satirical device]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsDevice Context triple: [Church Without Christ, usedAsDevice, satirical device]
-
A.
usedAsDeviceFor
Indicates that one entity functions as a tool, instrument, or device for performing an action or achieving a particular purpose for another entity.
-
B.
usesDevice
Indicates that one entity operates, employs, or relies on a particular device to perform an action or achieve a purpose.
-
C.
usedDesignDevice
Indicates that one entity employed or operated a particular design-related device or tool.
-
D.
usedVia
Indicates that an entity performs or achieves something by means of, or through the use of, another entity or mechanism.
-
E.
usedInDeviceModel
Indicates that something (such as a component, material, or technology) is utilized within or incorporated into a particular device model.
- 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_69f76db30a108190bb57ca95b873e5bb |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
| PDg | Predicate description generation | batch_69fe68a385f48190b942700e3eddc9b6 |
completed | May 8, 2026, 10:50 p.m. |
Created at: May 3, 2026, 3:59 p.m.