Triple
T28213146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helen |
E711230
|
entity |
| Predicate | drivesPlotDevelopmentIn |
P166207
|
FINISHED |
| Object | The Spare Room |
—
|
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: The Spare Room | Statement: [Helen, drivesPlotDevelopmentIn, The Spare Room]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drivesPlotDevelopmentIn Context triple: [Helen, drivesPlotDevelopmentIn, The Spare Room]
-
A.
showsDevelopmentOf
Indicates that one entity presents, illustrates, or makes evident the growth, progression, or evolution of another entity over time.
-
B.
aimsToDevelop
Indicates an entity’s intention or effort to create, improve, or bring about another entity, outcome, or capability.
-
C.
developsDuring
Indicates that one process, condition, or characteristic comes into existence or forms over the course of a specified time period, phase, or event.
-
D.
overseesDevelopmentOf
Indicates that one entity has responsibility for supervising, managing, or directing the development process of another entity.
-
E.
plannedDevelopment
Indicates that one entity has been designated or scheduled for future development or construction by another entity.
- 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_69efb51cb5288190818c1f63a266af11 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f66003a3f48190a2ba6da5aafbb5cb |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 27, 2026, 10:40 p.m.