Triple
T26428890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iris Simpkins |
E664446
|
entity |
| Predicate | relationshipStatusWithJasperBloom |
P196933
|
FINISHED |
| Object | unrequited love |
—
|
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: unrequited love | Statement: [Iris Simpkins, relationshipStatusWithJasperBloom, unrequited love]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipStatusWithJasperBloom Context triple: [Iris Simpkins, relationshipStatusWithJasperBloom, unrequited love]
-
A.
relationshipStatusWithJane
Indicates the current nature or state of an entity’s personal relationship with Jane.
-
B.
companionshipStatus
Indicates the current state or condition of a relationship of companionship between two or more entities.
-
C.
relationshipStatusInStory
Indicates the type or state of the relationship between entities as it exists within the context of a specific story or narrative.
-
D.
relationshipToQuiteria
Indicates the specific type of relationship or connection that an entity has to Quiteria.
-
E.
relationshipToJosephineBloom
Indicates the specific familial, social, or personal relationship that one entity has to Josephine Bloom.
- 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_69ee883ad6a4819088f918e76122d690 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fe6fea4a288190bf8615c5d6bf41b4 |
completed | May 8, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69fe6f774de08190975a2393b9a1fd22 |
completed | May 8, 2026, 11:19 p.m. |
| PDg | Predicate description generation | batch_69fe6fe98e38819085100ce4c6cee5b8 |
completed | May 8, 2026, 11:21 p.m. |
Created at: April 26, 2026, 11:47 p.m.