Triple
T619348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oracle of Apollo at Delphi |
E14476
|
entity |
| Predicate | consultationMethod |
P17183
|
FINISHED |
| Object | questions posed to Pythia |
—
|
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: questions posed to Pythia | Statement: [Oracle of Apollo at Delphi, consultationMethod, questions posed to Pythia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consultationMethod Context triple: [Oracle of Apollo at Delphi, consultationMethod, questions posed to Pythia]
-
A.
appointmentMethod
Indicates how an appointment is arranged, such as the channel, process, or means used to schedule it.
-
B.
communicationMode
Indicates the method or channel through which communication between entities is carried out.
-
C.
consultsOn
Indicates that one entity provides expert advice, guidance, or professional input to another entity regarding a specific subject, project, or decision.
-
D.
campaignMethod
Indicates the method or approach used to conduct or deliver a campaign.
-
E.
communicationChannel
Indicates a medium or method through which information is transmitted between parties.
- 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e25956c8190a1eed87002548658 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49cfe9bc081909a01b4b3b48f03b7 |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49def31ec81909dc53e70f4a36eda |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:35 p.m.