Triple
T12961008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosamond Vincy |
E310141
|
entity |
| Predicate | hasRomanticIdeal |
P69857
|
FINISHED |
| Object | elegant married life |
—
|
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: elegant married life | Statement: [Rosamond Vincy, hasRomanticIdeal, elegant married life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRomanticIdeal Context triple: [Rosamond Vincy, hasRomanticIdeal, elegant married life]
-
A.
romanticOutcome
Indicates that a romantic relationship or interaction between entities results in a particular outcome, such as success, failure, or change in status.
-
B.
hasIdeal
chosen
Indicates that an entity holds or is associated with a guiding principle, standard, or value it considers perfect or most desirable.
-
C.
loveInterestPortrayedBy
Indicates that a character’s romantic interest is depicted or played by a particular actor or performer.
-
D.
hasLoveLifeCharacteristic
Indicates that an entity possesses a particular quality, status, or attribute related to its romantic or love life.
-
E.
romanticArc
Indicates a developing or ongoing romantic relationship or storyline between the involved 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_69d7bdfb57a88190836b743e2825feca |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97dba57988190b786ffed55687a72 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:44 p.m.