Triple
T31624900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paradise Lost (oratorio) |
E806994
|
entity |
| Predicate | notableCharactersDepicted |
P64828
|
FINISHED |
| Object | God |
E6636
|
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: God | Statement: [Paradise Lost (oratorio), notableCharactersDepicted, God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCharactersDepicted Context triple: [Paradise Lost (oratorio), notableCharactersDepicted, God]
-
A.
notableCharacterType
Indicates that an entity is a notable or prominent example of a specified character type or role.
-
B.
notableForDepicting
Indicates that something is recognized or distinguished specifically for portraying or representing a particular subject, theme, or scene.
-
C.
notableDepictionBy
Indicates that an entity is significantly portrayed or represented by a particular creator, work, or medium.
-
D.
notableCharacterName
Indicates that the subject has a notable or significant character whose name is given by the object.
-
E.
notableWorkCharacter
chosen
Indicates that a character appears in, is associated with, or plays a role in a particular notable work.
- 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_69f348d7883c8190b6c13ab92b7ef076 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b5648a71c8190a7741768ed3c80f4 |
completed | June 12, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 10:42 p.m.