Triple
T32966252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Girl (Knemon’s daughter) |
E843377
|
entity |
| Predicate | workFirstPerformedAt |
P159799
|
FINISHED |
| Object | Lenaia festival |
—
|
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: Lenaia festival | Statement: [Girl (Knemon’s daughter), workFirstPerformedAt, Lenaia festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workFirstPerformedAt Context triple: [Girl (Knemon’s daughter), workFirstPerformedAt, Lenaia festival]
-
A.
workFirstPerformedIn
chosen
Indicates the place or context in which a particular work (such as a performance, composition, or production) was first performed.
-
B.
earliestOccupationDate
Indicates the earliest known date on which an entity began a particular occupation or role.
-
C.
workedFrom
Indicates that an entity was employed or actively engaged in work starting from a specified point in time.
-
D.
occupationBeganAfter
Indicates that one entity’s occupation or job role started at a later time than another specified event or occupation.
-
E.
workedPrimarilyOn
Indicates that an entity devoted the majority of its work, effort, or activity to a particular project, field, or subject.
- 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_69f3494af2808190ad98cec2f1bc0fe6 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d1a24e888190921a70d77cf06a05 |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:21 a.m.