Triple
T24872993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danny Martin |
E622485
|
entity |
| Predicate | relationshipEvolvesInto |
P115648
|
FINISHED |
| Object | serious 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: serious relationship | Statement: [Danny Martin, relationshipEvolvesInto, serious relationship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipEvolvesInto Context triple: [Danny Martin, relationshipEvolvesInto, serious relationship]
-
A.
relationshipDevelopsWith
Indicates that a relationship grows, evolves, or becomes more developed between two entities over time.
-
B.
relationshipDynamic
Indicates a changing or evolving pattern of interaction between entities, such as shifts in their roles, closeness, or influence over time.
-
C.
laterRelationshipWith
chosen
Indicates that one entity has a relationship with another that occurs at a later time relative to some reference point or prior relationship.
-
D.
relationshipOutcome
Indicates the result or consequence that arises from a particular relationship between two or more entities.
-
E.
relationshipType
Indicates the specific kind of relationship that exists between two or more 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_69e2fac3fdbc81909c2ec49be5743cd9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 18, 2026, 5:23 a.m.