Triple
T32164218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kat Ellis |
E821513
|
entity |
| Predicate | hiresPurpose |
P173653
|
FINISHED |
| Object | to pose as her boyfriend |
—
|
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: to pose as her boyfriend | Statement: [Kat Ellis, hiresPurpose, to pose as her boyfriend]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hiresPurpose Context triple: [Kat Ellis, hiresPurpose, to pose as her boyfriend]
-
A.
hires
Indicates that one entity employs or contracts another entity to perform work or services.
-
B.
meetsForPurpose
Indicates that one entity meets with another specifically to pursue or accomplish a particular purpose or objective.
-
C.
hiresRole
chosen
Indicates that an entity employs or brings on another entity specifically to perform a particular role or position.
-
D.
primaryUseOf
Indicates that one entity serves as the main or principal function, purpose, or application of another entity.
-
E.
tagPurpose
Indicates the intended role, function, or use associated with a given tag in a particular 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_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_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:33 a.m.