Triple
T1960717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyrrha |
E42378
|
entity |
| Predicate | ethnicRole |
P34425
|
FINISHED |
| Object | ancestress of the Hellenes |
—
|
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: ancestress of the Hellenes | Statement: [Pyrrha, ethnicRole, ancestress of the Hellenes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnicRole Context triple: [Pyrrha, ethnicRole, ancestress of the Hellenes]
-
A.
populationRole
Indicates the role or function that an entity has within a population or demographic context.
-
B.
urbanRole
Indicates the function, status, or role that an entity holds within an urban or city context.
-
C.
governmentalRole
Indicates that an entity holds or is assigned a specific official position, function, or authority within a government or public administration structure.
-
D.
electoralRole
Indicates the specific function, position, or capacity an entity holds within an electoral process or system.
-
E.
hasPoliticalRole
Indicates that an entity holds, has held, or is assigned a specific political office, function, or position in relation to another entity or 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_69a8870eea088190a38781990812a9bc |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb68a8e608190bc37a85913b3cd44 |
completed | March 7, 2026, 5:24 a.m. |
| PD | Predicate disambiguation | batch_69abaff5dbd48190a9d36ca60de151db |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb6893eb881908923f0168374596a |
completed | March 7, 2026, 5:24 a.m. |
Created at: March 4, 2026, 7:36 p.m.