Triple
T3282911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sethe |
E68912
|
entity |
| Predicate | relationshipTypeWithPaulD |
P38921
|
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: [Sethe, relationshipTypeWithPaulD, romantic relationship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipTypeWithPaulD Context triple: [Sethe, relationshipTypeWithPaulD, romantic relationship]
-
A.
relationshipType
Indicates the specific kind of relationship that exists between two or more entities.
-
B.
relationshipPlannedWith
Indicates that a relationship between two entities has been intentionally arranged or scheduled to occur in the future.
-
C.
hasPoliticalRelationshipWith
Indicates a political connection or association between two entities, such as alliances, rivalries, collaborations, or other forms of political interaction.
-
D.
relationshipToCharacter
chosen
Indicates the specific type of personal, social, or narrative connection that one entity has to a given character.
-
E.
portraysRelationship
Indicates that one entity depicts, represents, or illustrates a relationship between other 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_69ad859c463481909ca4be267336c290 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0345d448190a1f936abe7748e33 |
completed | March 8, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69ada421fadc8190b7c7d3c8afd20061 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.