Triple
T26076520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Athens (through the story of Theseus) |
E657699
|
entity |
| Predicate | offersRefugeTo |
P157841
|
FINISHED |
| Object | Oedipus |
—
|
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: Oedipus | Statement: [Athens (through the story of Theseus), offersRefugeTo, Oedipus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersRefugeTo Context triple: [Athens (through the story of Theseus), offersRefugeTo, Oedipus]
-
A.
grantedRefugeTo
chosen
Indicates that one entity provided shelter, protection, or safe haven to another entity, typically in a context of danger, persecution, or displacement.
-
B.
takenAsRefugeBy
Indicates that one entity is used or relied upon by another entity as a place or source of safety, protection, or refuge.
-
C.
designatedAsRefuge
Indicates that an entity has been officially assigned or recognized as a refuge or place of protection.
-
D.
tookRefugeWith
Indicates that one entity sought safety, protection, or shelter by going to and staying with another entity.
-
E.
offeredAid
Indicates that one entity provided or proposed help, support, or resources to 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 26, 2026, 7:34 p.m.