Triple
T12550026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mareva Grabowski-Mitsotaki |
E300072
|
entity |
| Predicate | publicRoleIn |
P90497
|
FINISHED |
| Object | Greek public life |
—
|
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: Greek public life | Statement: [Mareva Grabowski-Mitsotaki, publicRoleIn, Greek public life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicRoleIn Context triple: [Mareva Grabowski-Mitsotaki, publicRoleIn, Greek public life]
-
A.
antRole
chosen
Indicates that one entity has a specific role, function, or responsibility in relation to another entity.
-
B.
possibleRole
Indicates that an entity is capable of or eligible to serve in a particular role or function in a given context.
-
C.
impliesRole
Indicates that one role logically entails or gives rise to another role within a given context or system.
-
D.
canonicalRole
Indicates that an entity holds a standard, primary, or officially recognized role within a particular context or system.
-
E.
secretRole
Indicates that an entity holds a role or function that is intentionally hidden or not publicly disclosed within a given context.
- 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_69d6ada707008190aaec1238117c9379 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d95410d0b0819097646edd1b837104 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:58 p.m.