Triple
T31703133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eddie |
E809110
|
entity |
| Predicate | relationshipTypeWithMay |
P10690
|
FINISHED |
| Object | romantic relationship |
—
|
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: romantic relationship | Statement: [Eddie, relationshipTypeWithMay, romantic relationship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipTypeWithMay Context triple: [Eddie, relationshipTypeWithMay, romantic relationship]
-
A.
relationshipType
chosen
Indicates the specific kind of relationship that exists between two or more entities.
-
B.
haveRelationshipWith
Indicates that one entity is in some form of defined relationship or association with another entity.
-
C.
relationshipTypeStart
Indicates the type or category of relationship that begins or is initiated at a specific point or event.
-
D.
inRelationshipWith
Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
-
E.
mayRelateTo
Indicates a possible, but not certain, relationship or association between two entities.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 11:12 p.m.