Triple
T20651981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sophie Chapman |
E507516
|
entity |
| Predicate | relationshipTypeWithMarkCorrigan |
P140926
|
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: [Sophie Chapman, relationshipTypeWithMarkCorrigan, romantic relationship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipTypeWithMarkCorrigan Context triple: [Sophie Chapman, relationshipTypeWithMarkCorrigan, romantic relationship]
-
A.
relationshipToMacCory
Indicates the specific type of relationship or connection an entity has to MacCory.
-
B.
relationshipToCoraMunro
Indicates the specific type of personal or social relationship an entity has with Cora Munro.
-
C.
relationshipWithNickCurran
Indicates that an entity has some form of relationship or connection with Nick Curran.
-
D.
relationshipTypeWithTristan
Indicates the specific nature or category of the relationship that an entity has with Tristan.
-
E.
relationshipToTristan
Indicates the specific type of personal, social, or familial connection that one entity has with the individual named Tristan.
- F. None of above. chosen
Provenance (4 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_69e0b4bf58c081908e52a4500e03ff83 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6af22d6bc8190b9d6877aba5704eb |
completed | April 20, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3caef50819093c8159fe8d6435b |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 11:43 a.m.