Triple
T5860374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chiron |
E130259
|
entity |
| Predicate | gaveUpImmortalityFor |
P18946
|
FINISHED |
| Object | releaseOfPrometheus |
—
|
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: releaseOfPrometheus | Statement: [Chiron, gaveUpImmortalityFor, releaseOfPrometheus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gaveUpImmortalityFor Context triple: [Chiron, gaveUpImmortalityFor, releaseOfPrometheus]
-
A.
immortality
Indicates that an entity possesses the quality of never dying or ceasing to exist, persisting indefinitely through time.
-
B.
becomesImmortalIn
Indicates that an entity transitions into a state of immortality within a specified context, time, or medium.
-
C.
sacrificedTo
Indicates that one entity is offered or given up as a sacrifice in honor of, or to appease, another entity.
-
D.
sharesImmortalityWith
Indicates that one entity grants or mutually possesses an immortal or deathless state together with another entity.
-
E.
sacrifice
chosen
Indicates giving up something of value, often for the benefit, protection, or advantage of another entity or goal.
- 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_69c0084f3bb08190a7720f55f7aa4252 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03345ca0c819081c81148d054fed2 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:56 p.m.