Triple
T33265198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proteus |
E851624
|
entity |
| Predicate | laterInLoveWith |
P153136
|
FINISHED |
| Object | Silvia |
—
|
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: Silvia | Statement: [Proteus, laterInLoveWith, Silvia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterInLoveWith Context triple: [Proteus, laterInLoveWith, Silvia]
-
A.
laterLoves
chosen
Indicates that one entity comes to love another at a later time than some referenced point or event.
-
B.
fellInLoveWith
Indicates that one entity developed romantic love or deep affectionate feelings toward another entity.
-
C.
laterIn
Indicates that one event, state, or time point occurs after another in temporal order.
-
D.
loveInterestPortrayedBy
Indicates that a character’s romantic interest is depicted or played by a particular actor or performer.
-
E.
initiallyEngagedTo
Indicates that one entity was first formally promised or committed to marry another entity at the beginning of a specified time or event.
- 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_69ffde9263248190996f970b6cf6e49d |
completed | May 10, 2026, 1:25 a.m. |
| PD | Predicate disambiguation | batch_69ffdd760f1c8190abc6c0c1cd97ba5f |
completed | May 10, 2026, 1:20 a.m. |
Created at: May 1, 2026, 1:32 a.m.