Triple
T33265196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proteus |
E851624
|
entity |
| Predicate | formerSuitorOf |
P162062
|
FINISHED |
| Object | Julia |
—
|
NE NERFINISHED |
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: Julia | Statement: [Proteus, formerSuitorOf, Julia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerSuitorOf Context triple: [Proteus, formerSuitorOf, Julia]
-
A.
formerRomanticInterest
chosen
Indicates that one entity previously had a romantic relationship or attraction toward another entity, but that romantic connection has since ended.
-
B.
formerFiancéeOf
Indicates that one person was previously engaged to be married to another person, but the engagement has since ended.
-
C.
initiallyEngagedTo
Indicates that one entity was first formally promised or committed to marry another entity at the beginning of a specified time or event.
-
D.
proposedBride
Indicates that one entity has been put forward or suggested as a potential bride for another entity.
-
E.
hasFianceeOfSonAsLover
Indicates that a person is in a romantic or sexual relationship with their son’s fiancée.
- 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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffb69812808190a751853b30183e65 |
completed | May 9, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69ffb63bdda88190a9dd8426dc0bad43 |
completed | May 9, 2026, 10:33 p.m. |
Created at: May 1, 2026, 1:32 a.m.