Triple
T5860373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chiron |
E130259
|
entity |
| Predicate | famousEpisode |
P2757
|
FINISHED |
| Object | exchangeOfImmortalityWithPrometheus |
—
|
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: exchangeOfImmortalityWithPrometheus | Statement: [Chiron, famousEpisode, exchangeOfImmortalityWithPrometheus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousEpisode Context triple: [Chiron, famousEpisode, exchangeOfImmortalityWithPrometheus]
-
A.
notableEpisode
chosen
Indicates that a particular episode is especially significant, memorable, or noteworthy in relation to the subject.
-
B.
hasEpisodeAbout
Indicates that a particular episode (such as of a show, podcast, or series) focuses on, discusses, or is centered around a specified subject or topic.
-
C.
associatedEpisode
Indicates that one entity is linked or connected to a particular episode as its related or relevant installment.
-
D.
narrativeEpisode
Indicates that one event, scene, or segment functions as a distinct episode within a larger narrative or storyline.
-
E.
famousProgram
Indicates that a program is widely recognized or well-known, typically for its impact, quality, or popularity.
- 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.