Triple
T26630120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plumette |
E668466
|
entity |
| Predicate | romanticSceneWith |
P162168
|
FINISHED |
| Object | Lumière |
—
|
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: Lumière | Statement: [Plumette, romanticSceneWith, Lumière]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanticSceneWith Context triple: [Plumette, romanticSceneWith, Lumière]
-
A.
romanticLeadIn
Indicates that one entity is the primary romantic interest or central romantic partner of another within a narrative or context.
-
B.
romanticPattern
Indicates a recurring style, tendency, or structure in how romantic relationships or attractions develop or are expressed between entities.
-
C.
romanticThemeExpressedThrough
Indicates that a romantic theme is conveyed or manifested through a particular medium, element, or aspect of a work or situation.
-
D.
romanticArc
Indicates a developing or ongoing romantic relationship or storyline between the involved entities.
-
E.
hasRomanticSceneAt
Indicates that a romantic scene occurs at a specific location or point in time within a work or context.
- 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_69ee9cff507c819092b95bf7219a702e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f622abdfac8190988421c946411d7e |
completed | May 2, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621fbfc2c8190bfa802d7dc0f6aa4 |
completed | May 2, 2026, 4:10 p.m. |
Created at: April 27, 2026, 2:24 a.m.