Triple
T37154673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nimmie Amee |
E920460
|
entity |
| Predicate | formerSweetheartOf |
P162062
|
FINISHED |
| Object | Tin Woodman |
—
|
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: Tin Woodman | Statement: [Nimmie Amee, formerSweetheartOf, Tin Woodman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerSweetheartOf Context triple: [Nimmie Amee, formerSweetheartOf, Tin Woodman]
-
A.
isChildhoodSweetheartOf
Indicates that two people were romantically involved with each other during their childhood or adolescence, typically as first or early sweethearts.
-
B.
formerFiancéeOf
Indicates that one person was previously engaged to be married to another person, but the engagement has since ended.
-
C.
rumoredLoverOf
Indicates that one entity is widely believed or speculated to be the romantic partner or lover of another entity, without confirmed evidence.
-
D.
isFianceeOf
Indicates that one person is the engaged-to-be-married partner of another person.
-
E.
formerRomanticInterest
chosen
Indicates that one entity previously had a romantic relationship or attraction toward another entity, but that romantic connection has since ended.
- 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_69f76e9f87c08190b4c8f7fafbd8345a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00c486d394819084fe93d5bb11ea1e |
completed | May 10, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_6a00c39d99d48190a94bfa057213499c |
completed | May 10, 2026, 5:42 p.m. |
Created at: May 3, 2026, 4:15 p.m.