Triple
T11458370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alice Sycamore |
E271585
|
entity |
| Predicate | loveInterestRelationshipType |
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: [Alice Sycamore, loveInterestRelationshipType, romantic relationship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loveInterestRelationshipType Context triple: [Alice Sycamore, loveInterestRelationshipType, romantic relationship]
-
A.
loveInterest
Indicates that one entity is the romantic object of affection or attraction for another entity.
-
B.
loveInterestPortrayedBy
Indicates that a character’s romantic interest is depicted or played by a particular actor or performer.
-
C.
relationshipDevelopsWith
Indicates that a relationship grows, evolves, or becomes more developed between two entities over time.
-
D.
relationshipType
chosen
Indicates the specific kind of relationship that exists between two or more entities.
-
E.
relationshipDynamic
Indicates a changing or evolving pattern of interaction between entities, such as shifts in their roles, closeness, or influence over time.
- 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_69d6aadff8888190a13f253f0d460874 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d822f2138081909408c7916cef99c9 |
completed | April 9, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69d80867ff248190bb157fa9e355353b |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:35 p.m.