Triple
T35819006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rupert Sheldrake |
E1035443
|
entity |
| Predicate | hasNotableDebateWith |
P64392
|
FINISHED |
| Object | Richard Dawkins |
E93005
|
NE 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: Richard Dawkins | Statement: [Rupert Sheldrake, hasNotableDebateWith, Richard Dawkins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableDebateWith Context triple: [Rupert Sheldrake, hasNotableDebateWith, Richard Dawkins]
-
A.
hasNotableDebates
Indicates that there have been significant or widely recognized debates or controversies involving the related entities.
-
B.
hasDebateAround
Indicates that there is ongoing discussion, disagreement, or controversy surrounding the referenced entity or topic.
-
C.
hasDebatedPerson
chosen
Indicates that one person has engaged in a debate or formal argumentative discussion with another person.
-
D.
hasDebate
Indicates that there is a formal discussion or argument between entities, typically presenting opposing viewpoints on a topic.
-
E.
hasLongTermDebateOn
Indicates that there is an ongoing, extended period of discussion, disagreement, or argument concerning a particular topic or issue.
- F. None of above.
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_69f76e185ffc8190880b3cdf51decd38 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3891792bf0819098f892061f2249ab |
completed | June 22, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.