Triple
T12751102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Pen |
E304730
|
entity |
| Predicate | rejectsAccusation |
P59948
|
FINISHED |
| Object | madness of the Prophet |
—
|
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: madness of the Prophet | Statement: [The Pen, rejectsAccusation, madness of the Prophet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rejectsAccusation Context triple: [The Pen, rejectsAccusation, madness of the Prophet]
-
A.
rejectsAssumption
Indicates that one entity explicitly refuses to accept or denies the validity of a proposed assumption made by another entity.
-
B.
rejectedJustification
Indicates that a proposed justification or reason offered in a context (e.g., argument, decision, or claim) has been evaluated and not accepted as valid or sufficient.
-
C.
reactionToAccusation
chosen
Indicates how an entity responds or behaves when confronted with an accusation made by another entity.
-
D.
rejectedIn
Indicates that an entity or proposal was not accepted or was turned down within a specific context, process, or location.
-
E.
rejectedBy
Indicates that one entity has been refused, dismissed, or not accepted by 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96406e97c8190b79081039847115c |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:27 p.m.