Triple
T34409048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jamie |
E883201
|
entity |
| Predicate | relationshipToLoveInterest |
P205426
|
FINISHED |
| Object | employer of housekeeper |
—
|
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: employer of housekeeper | Statement: [Jamie, relationshipToLoveInterest, employer of housekeeper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToLoveInterest Context triple: [Jamie, relationshipToLoveInterest, employer of housekeeper]
-
A.
relationshipDynamic
Indicates a changing or evolving pattern of interaction between entities, such as shifts in their roles, closeness, or influence over time.
-
B.
relationshipToLady
Indicates the specific type of social, familial, or personal connection that one entity has to a lady.
-
C.
relationshipDevelopsWith
Indicates that a relationship grows, evolves, or becomes more developed between two entities over time.
-
D.
relationshipToHeed
Indicates a relationship in which one entity is expected to pay attention to, respect, or follow the guidance, warnings, or wishes of another entity.
-
E.
relationshipToFriends
Indicates the type or nature of the relationship an entity has with its friends.
- 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_69f349c1f2208190a09a489bb8b2719d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:59 a.m.