Triple
T35699565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hume Variations |
E1031538
|
entity |
| Predicate | hasCentralFigureDiscussed |
P58604
|
FINISHED |
| Object | David Hume |
—
|
NE NERFINISHED |
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: David Hume | Statement: [Hume Variations, hasCentralFigureDiscussed, David Hume]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralFigureDiscussed Context triple: [Hume Variations, hasCentralFigureDiscussed, David Hume]
-
A.
hasCentralFigure
Indicates that something features a primary or most important figure at its core or focus.
-
B.
discussesFigure
chosen
Indicates that one entity engages in discussion or analysis specifically about a particular figure (such as a person, character, or notable individual).
-
C.
hasMainCharacterDiscussed
Indicates that the main character has engaged in a discussion or conversation about a particular subject or with another entity.
-
D.
discussedAs
Indicates that one entity is talked about, treated, or examined in terms of another entity, often as an example, case, or framing concept.
-
E.
centralFigureTrait
Indicates that a particular trait or characteristic is associated with the central or primary figure in a given context.
- 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_69f76e0d393c8190b6303c64408736db |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.