Triple
T17977284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dylan Harper |
E449507
|
entity |
| Predicate | engagesInRelationshipType |
P10690
|
FINISHED |
| Object | no-strings-attached 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: no-strings-attached relationship | Statement: [Dylan Harper, engagesInRelationshipType, no-strings-attached relationship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engagesInRelationshipType Context triple: [Dylan Harper, engagesInRelationshipType, no-strings-attached relationship]
-
A.
inRelationshipWith
Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
-
B.
relationshipType
chosen
Indicates the specific kind of relationship that exists between two or more entities.
-
C.
worksInCloseRelationshipWith
Indicates a collaborative professional relationship in which two or more entities work together closely and interact frequently to achieve shared goals.
-
D.
showsRelationshipWith
Indicates that one entity visually or explicitly presents or demonstrates its connection or association with another entity.
-
E.
hasMaritalRelationshipType
Indicates the specific type or nature of the marital relationship that exists 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b20010c8819088c022565183a7ff |
completed | April 19, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:22 a.m.