Triple
T32164217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kat Ellis |
E821513
|
entity |
| Predicate | hiresRole |
P173653
|
FINISHED |
| Object | male escort |
—
|
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: male escort | Statement: [Kat Ellis, hiresRole, male escort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hiresRole Context triple: [Kat Ellis, hiresRole, male escort]
-
A.
higherFormationRole
Indicates that an entity serves in a specific role or function within a larger, higher-level organizational formation.
-
B.
highlightsRole
Indicates that one entity emphasizes, showcases, or draws special attention to the role or function of another entity.
-
C.
HodRole
Indicates that an entity holds the role or position of Head of Department (HOD) in relation to a specified department or organizational unit.
-
D.
managementRole
Indicates that one entity holds a managerial or supervisory role with authority and responsibility over another entity.
-
E.
highWaterMarkRole
Indicates that an entity holds the role responsible for tracking, maintaining, or representing the highest recorded level or peak value within a given 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_69f3490699a48190bbef96b198e8fade |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6ba1e9d5c81908ba549e95fca3c93 |
completed | May 3, 2026, 2:59 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:33 a.m.