Triple
T37683563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pope Sylvester II |
E938302
|
entity |
| Predicate | allegedIn |
P191740
|
FINISHED |
| Object | legends about magic and the devil |
—
|
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: legends about magic and the devil | Statement: [Pope Sylvester II, allegedIn, legends about magic and the devil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedIn Context triple: [Pope Sylvester II, allegedIn, legends about magic and the devil]
-
A.
allegedStatus
Indicates that a particular status or condition is claimed or asserted about an entity, but has not been confirmed as true.
-
B.
allegedClause
Indicates that a clause or statement is claimed or asserted to be true, typically without confirmed proof or legal determination.
-
C.
allegedAction
Indicates that an action is claimed or asserted to have occurred, typically without being proven or confirmed.
-
D.
accusedIn
Indicates that a person or entity is formally charged with wrongdoing in a particular case, proceeding, or context.
-
E.
allegedUse
Indicates that something is claimed or suspected to have been used, without confirming that the use actually occurred.
- 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_69f76ed881408190bc62a969530a4a53 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
| PDg | Predicate description generation | batch_69fce76669408190b1beef8899a8a5e2 |
completed | May 7, 2026, 7:26 p.m. |
Created at: May 3, 2026, 4:18 p.m.