Triple
T33218650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Woman from Sicyon |
E850357
|
entity |
| Predicate | settingImpliedByTitle |
P189467
|
FINISHED |
| Object | Sicyon |
—
|
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: Sicyon | Statement: [The Woman from Sicyon, settingImpliedByTitle, Sicyon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingImpliedByTitle Context triple: [The Woman from Sicyon, settingImpliedByTitle, Sicyon]
-
A.
titleImplies
Indicates that holding or being assigned a particular title suggests or entails a certain role, status, or set of responsibilities.
-
B.
usesTitle
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
-
C.
usesTitleIn
Indicates that an entity is referred to using a particular title within a specified context or medium.
-
D.
subjectImpliedAs
Indicates that the subject of an action or statement is not explicitly stated but is understood or inferred from context.
-
E.
linealTitleImplication
Indicates that a particular lineal (hereditary or ancestral) title entails or implies another status, rank, or entitlement in a genealogical or succession context.
- 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_69f3496083dc8190b229bb6932dc548b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: May 1, 2026, 1:30 a.m.