Triple
T20832689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LWV 53 |
E512870
|
entity |
| Predicate | hasKeyRoleInWork |
P101358
|
FINISHED |
| Object | title role Atys |
—
|
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: title role Atys | Statement: [LWV 53, hasKeyRoleInWork, title role Atys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyRoleInWork Context triple: [LWV 53, hasKeyRoleInWork, title role Atys]
-
A.
hasRoleInWorkType
Indicates that an entity holds a specific role or function within a particular type or category of work.
-
B.
hasKeyWork
Indicates that an entity possesses or is associated with a primary or central work (such as a main publication, artwork, or project) that is especially representative or important.
-
C.
isKeyRole
chosen
Indicates that an entity holds a primary or critically important role within a given context or structure.
-
D.
hasWorkInSeriesRole
Indicates that an entity holds a specific role or function within a particular work that is part of a series.
-
E.
hasWorksIn
Indicates that one entity is employed by or performs their professional activities within the organization, location, or context represented by another entity.
- 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_69e0b4cf62a88190bbf92351e9e57259 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c3235a7c8190a00dbd7008cf107a |
completed | April 21, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a1f4f48190aa9fb4ef8f8aea5a |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:42 p.m.