Triple
T27817557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edwin Drood |
E702715
|
entity |
| Predicate | hasScholarlyDebateAbout |
P40843
|
FINISHED |
| Object | fate of Edwin Drood |
—
|
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: fate of Edwin Drood | Statement: [Edwin Drood, hasScholarlyDebateAbout, fate of Edwin Drood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScholarlyDebateAbout Context triple: [Edwin Drood, hasScholarlyDebateAbout, fate of Edwin Drood]
-
A.
inAcademicDebate
chosen
Indicates that one entity is engaged in a formal, scholarly argument or discussion with another entity, typically following academic norms and methods of reasoning.
-
B.
hasDebateAround
Indicates that there is ongoing discussion, disagreement, or controversy surrounding the referenced entity or topic.
-
C.
hasSourceOfDebate
Indicates that something is the origin or cause of an ongoing disagreement, controversy, or dispute between parties.
-
D.
debatedWithin
Indicates that something is discussed or argued about within a particular group, context, or domain.
-
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 (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_69ef840ad1e88190b5bff2d1ddec8700 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 27, 2026, 5:46 p.m.