Triple
T8546573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marina |
E202340
|
entity |
| Predicate | relationshipStatusWithHoward |
P83243
|
FINISHED |
| Object | extramarital affair (implied) |
—
|
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: extramarital affair (implied) | Statement: [Marina, relationshipStatusWithHoward, extramarital affair (implied)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipStatusWithHoward Context triple: [Marina, relationshipStatusWithHoward, extramarital affair (implied)]
-
A.
relationshipToHannah
Indicates the specific type of relationship or connection that an entity has to Hannah.
-
B.
relationshipStatusWithBrian
Indicates the current nature or state of an entity’s personal relationship with Brian.
-
C.
relationshipStatusWithDrEvil
Indicates the type or state of a person's relationship with Dr. Evil.
-
D.
inRelationshipWith
Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
-
E.
relationshipToNaomi
Indicates the specific familial, social, or interpersonal connection that an entity has with Naomi.
- 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_69ca832461e88190a654c5e44e233aa8 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe7511f8c819083d69fb6a0b55801 |
completed | March 31, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69cbd113e05c81908f4f3fc1b5925164 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30d453481908f897ed2b06e7534 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:19 p.m.