Triple
T16549267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanctuary of Apollo at Pherae |
E402025
|
entity |
| Predicate | hasConsultationMethod |
P17183
|
FINISHED |
| Object | oracular consultation |
—
|
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: oracular consultation | Statement: [Sanctuary of Apollo at Pherae, hasConsultationMethod, oracular consultation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConsultationMethod Context triple: [Sanctuary of Apollo at Pherae, hasConsultationMethod, oracular consultation]
-
A.
consultationMethod
chosen
Indicates the way or medium through which a consultation is conducted or delivered.
-
B.
hasConsultants
Indicates that one entity engages or employs another entity to provide professional consulting services.
-
C.
appointmentMethod
Indicates how an appointment is arranged, such as the channel, process, or means used to schedule it.
-
D.
hasContactMethod
Indicates that an entity has a specific way or channel through which it can be contacted.
-
E.
requiresConsultationWith
Indicates that performing an action or making a decision depends on first obtaining input, approval, or advice from a specified party.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e34fc323a88190b5c2a34de0a3c7f0 |
completed | April 18, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69e2969fab208190ad64164d24748c45 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:15 a.m.