Triple
T15126655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kathryn Hays |
E361306
|
entity |
| Predicate | endedRoleAsKimHughes |
P117429
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Kathryn Hays, endedRoleAsKimHughes, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endedRoleAsKimHughes Context triple: [Kathryn Hays, endedRoleAsKimHughes, 2010]
-
A.
representedRole
Indicates that one entity serves as a stand-in, proxy, or representative performing a role on behalf of another entity.
-
B.
playRoleIn
Indicates that an entity participates in or performs a specific function, character, or part within an event, context, or system.
-
C.
emotionalRole
Indicates a relationship where one entity holds a particular emotional significance, function, or impact in relation to another entity.
-
D.
perceivedRole
Indicates the role or function that one entity is regarded or interpreted as having in relation to another, based on perception rather than objective status.
-
E.
honorsRoleAs
Indicates that one entity shows respect, recognition, or deference to another entity specifically in their official position or function.
- 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005a1b9288190954f2d92549805e5 |
completed | April 15, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69deb9713fe881909dec2fd3f6c84b39 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec71e8dcc81908badc834b6ccf273 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:06 a.m.