Triple
T35116561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Augustine Guillaume |
E1013453
|
entity |
| Predicate | romanticIdeal |
P183548
|
FINISHED |
| Object | artistic, passionate love |
—
|
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: artistic, passionate love | Statement: [Augustine Guillaume, romanticIdeal, artistic, passionate love]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanticIdeal Context triple: [Augustine Guillaume, romanticIdeal, artistic, passionate love]
-
A.
romanticallyIdealizedBy
Indicates that one entity is viewed or portrayed by another as a perfect or ideal romantic partner, often in an unrealistic or idealized way.
-
B.
romanticArc
Indicates a developing or ongoing romantic relationship or storyline between the involved entities.
-
C.
romanticallyObsessedWith
Indicates a strong, often overwhelming romantic fixation or preoccupation that one entity has toward another.
-
D.
romanticFeeling
Indicates that one entity experiences romantic attraction or affection toward another entity.
-
E.
romanticPattern
Indicates a recurring style, tendency, or structure in how romantic relationships or attractions develop or are expressed between entities.
- 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_69f76dd659d08190bcdc00d37caafb62 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7a01efcc08190bba489a9099b8684 |
completed | May 3, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79f477c4c8190a35cb6d87b1dcbd1 |
completed | May 3, 2026, 7:17 p.m. |
Created at: May 3, 2026, 4:01 p.m.