Triple
T26076253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perigune |
E657689
|
entity |
| Predicate | postEventRelationship |
P84094
|
FINISHED |
| Object | becomes consort of Theseus after Sinis is slain |
—
|
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: becomes consort of Theseus after Sinis is slain | Statement: [Perigune, postEventRelationship, becomes consort of Theseus after Sinis is slain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postEventRelationship Context triple: [Perigune, postEventRelationship, becomes consort of Theseus after Sinis is slain]
-
A.
relationshipStartEvent
chosen
Indicates the event or point in time at which a particular relationship between entities begins.
-
B.
createsRelationshipWith
Indicates that one entity establishes or initiates a new relationship or association with another entity.
-
C.
relationshipToEvent
Indicates the specific way an entity is connected or related to a particular event.
-
D.
associatedEventType
Indicates that one entity is linked to another by the type or category of event with which it is associated.
-
E.
laterRelatedEvent
Indicates that one event is temporally related to another by occurring at a later time.
- 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_69f606cf938c8190aa96a095c824367e |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 7:34 p.m.