Triple
T4377717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heraia |
E99047
|
entity |
| Predicate | organizers |
P56473
|
FINISHED |
| Object | 16 women from Elis |
—
|
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: 16 women from Elis | Statement: [Heraia, organizers, 16 women from Elis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizers Context triple: [Heraia, organizers, 16 women from Elis]
-
A.
organizes
Indicates that one entity arranges, coordinates, or structures activities, items, or people into an ordered or planned form for a particular purpose.
-
B.
organizerRole
Indicates that an entity has the role or responsibility of organizing an event, activity, or group.
-
C.
oftenOrganizedBy
Indicates that an event, activity, or process is frequently arranged, coordinated, or hosted by a particular agent or entity.
-
D.
principalOrganizer
Indicates that an entity serves as the main or leading organizer responsible for planning or coordinating another entity or event.
-
E.
firstOrganizer
Indicates that an entity serves as the primary or initial organizer in relation to another event, group, or activity.
- 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_69b3454ea8f48190a49c2436624d6ef6 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3523ed220819090cef1a7933489d9 |
completed | March 12, 2026, 11:54 p.m. |
| PD | Predicate disambiguation | batch_69b34f557fe8819085032bf7f0cea5dc |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b35034cd248190bae09e9d090e13ec |
completed | March 12, 2026, 11:45 p.m. |
Created at: March 12, 2026, 11:18 p.m.