Triple
T36361505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terrence "Scooter" Williams |
E895504
|
entity |
| Predicate | hasRomanticArcIn |
P10693
|
FINISHED |
| Object | Living Single |
—
|
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: Living Single | Statement: [Terrence "Scooter" Williams, hasRomanticArcIn, Living Single]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRomanticArcIn Context triple: [Terrence "Scooter" Williams, hasRomanticArcIn, Living Single]
-
A.
hasRomanticEntanglementInPlot
Indicates that a romantic relationship or involvement between characters is a significant element within the narrative plot.
-
B.
hasRomanticPlotline
Indicates that there is a romantic storyline or relationship development present between the entities.
-
C.
hasRomanticSubplot
Indicates that a work includes a secondary storyline centered on a romantic relationship between characters.
-
D.
romanticArc
chosen
Indicates a developing or ongoing romantic relationship or storyline between the involved entities.
-
E.
hasRomanticTensionWith
Indicates a mutual or one-sided romantic attraction or unresolved romantic interest existing between two 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_69f76e5044248190b390d8887dc03254 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fec00f27988190955de6b6348a4d97 |
completed | May 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69febd52037c8190b475dbd50fdbc13e |
completed | May 9, 2026, 4:51 a.m. |
Created at: May 3, 2026, 4:09 p.m.