Triple
T36407122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Modern Prometheus |
E896775
|
entity |
| Predicate | refersToCharacterAs |
P60518
|
FINISHED |
| Object | a modern Prometheus |
—
|
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: a modern Prometheus | Statement: [The Modern Prometheus, refersToCharacterAs, a modern Prometheus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToCharacterAs Context triple: [The Modern Prometheus, refersToCharacterAs, a modern Prometheus]
-
A.
refersToCharacter
chosen
Indicates that one entity makes reference to, mentions, or points to a specific character as its subject.
-
B.
refersToCharacterStatus
Indicates that one entity references or denotes the status or condition of a specific character.
-
C.
refersToPerson
Indicates that one entity is making reference to, mentioning, or pointing specifically to a particular person.
-
D.
characterAlias
Indicates that one character is known or referred to by an alternative name or alias.
-
E.
namedAfterFictionalCharacter
Indicates that one entity has been given its name in honor of, or derived from, a fictional character.
- 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_69f76e53b81081908d3b81860593f38a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69feb342994081909481ec8ec5d44928 |
completed | May 9, 2026, 4:08 a.m. |
| PD | Predicate disambiguation | batch_69feb046e4e48190b96649aa28529cc9 |
completed | May 9, 2026, 3:55 a.m. |
Created at: May 3, 2026, 4:10 p.m.