Triple
T27696541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oasis of Siwa |
E698308
|
entity |
| Predicate | hasOracleDedicatedTo |
P63273
|
FINISHED |
| Object | Amun |
—
|
NE NERFINISHED |
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: Amun | Statement: [Oasis of Siwa, hasOracleDedicatedTo, Amun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOracleDedicatedTo Context triple: [Oasis of Siwa, hasOracleDedicatedTo, Amun]
-
A.
hasOracleOf
chosen
Indicates that one entity serves as a prophetic or divinatory source (an oracle) for another entity.
-
B.
associatedWithOracle
Indicates a relationship where an entity is connected, linked, or otherwise related to Oracle (e.g., the Oracle company, technology, or ecosystem) in some relevant way.
-
C.
linkedToOracle
Indicates that one entity is connected or associated with an Oracle system, service, or resource.
-
D.
guaranteeOnOracle
Indicates that one party provides a guarantee or assurance contingent upon the outcome or information supplied by an oracle.
-
E.
includesOracleAgainst
Indicates that one entity contains or incorporates an oracle or prophetic judgment directed against another entity.
- 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_69ef590ea74081908f0cd7500d85fa27 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 27, 2026, 2:54 p.m.