Triple
T869647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prometheus Bound |
E18780
|
entity |
| Predicate | portrayalOfZeus |
P5782
|
FINISHED |
| Object | tyrannical ruler |
—
|
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: tyrannical ruler | Statement: [Prometheus Bound, portrayalOfZeus, tyrannical ruler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portrayalOfZeus Context triple: [Prometheus Bound, portrayalOfZeus, tyrannical ruler]
-
A.
mythologicalRole
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
-
B.
representsDeity
chosen
Indicates that one entity serves as a symbolic, artistic, or conceptual depiction of a deity associated with another entity.
-
C.
portraysActorAs
Indicates that one entity depicts or represents an actor in a particular role, character, or manner.
-
D.
oftenDepictedAs
Indicates that one entity is frequently represented or portrayed in the form, appearance, or symbolism of another entity.
-
E.
typeOfDeity
Indicates that one entity is classified as a specific kind or category of deity in relation to another.
- 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_69a4938ce8688190a24bdfef82ba7d21 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac811e548190a72b7a10b5ea8665 |
completed | March 1, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69a4aa89ca008190b50d061ac7fe19f9 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.