Triple
T29936066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alyssa Jones |
E760363
|
entity |
| Predicate | relationshipComplexity |
P47731
|
FINISHED |
| Object | complex romantic history |
—
|
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: complex romantic history | Statement: [Alyssa Jones, relationshipComplexity, complex romantic history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipComplexity Context triple: [Alyssa Jones, relationshipComplexity, complex romantic history]
-
A.
relationshipDynamic
Indicates a changing or evolving pattern of interaction between entities, such as shifts in their roles, closeness, or influence over time.
-
B.
relationshipImpact
Indicates how one entity’s relationship with another affects or changes those entities or their interaction.
-
C.
hasComplicatedRelationshipWith
chosen
Indicates that one entity is involved in a complex, often ambiguous or difficult-to-define interpersonal or relational dynamic with another entity.
-
D.
relationshipFocus
Indicates a relationship where particular attention, priority, or emphasis is placed on the connection between two or more entities.
-
E.
relationshipScope
Indicates the contextual boundaries or extent within which a particular relationship between entities is defined or considered valid.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a01cb89ff448190b60ee3d148ce76fc |
completed | May 11, 2026, 12:28 p.m. |
| PD | Predicate disambiguation | batch_6a01ca7604b48190bb8643c17c3a8c85 |
completed | May 11, 2026, 12:24 p.m. |
Created at: April 29, 2026, 6:20 p.m.