Triple
T3658314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | slaying of Python by Apollo |
E77586
|
entity |
| Predicate | ApolloDomain |
P50184
|
FINISHED |
| Object | prophecy |
—
|
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: prophecy | Statement: [slaying of Python by Apollo, ApolloDomain, prophecy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ApolloDomain Context triple: [slaying of Python by Apollo, ApolloDomain, prophecy]
-
A.
activityDomain
Indicates the general field, sector, or area of activity within which an entity operates or performs its main actions.
-
B.
spaceDomain
Indicates that the relationship or activity occurs within, pertains to, or is governed by the space domain (outer space and related space operations).
-
C.
assistant
Indicates that one entity provides help, support, or services to another entity.
-
D.
coPilotWith
Indicates that two entities jointly serve as pilots or share piloting responsibilities for the same vehicle or mission.
-
E.
coPilotOf
Indicates that one entity serves as the co-pilot assisting and supporting another entity in operating or navigating a vehicle or craft.
- F. None of above. chosen
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_69ad85def5cc8190863dccf55a18bebb |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3d48a2081908ac0f76d548a53ee |
completed | March 8, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69adb847e9d881909dad2ffd0f3b6c15 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb97cdb788190a5ce96b21bd157ab |
completed | March 8, 2026, 6:01 p.m. |
Created at: March 8, 2026, 3:24 p.m.