Triple
T32877313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1313 Mockingbird Lane |
E840962
|
entity |
| Predicate | reusedAsSetIn |
P91997
|
FINISHED |
| Object | Desperate Housewives |
—
|
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: Desperate Housewives | Statement: [1313 Mockingbird Lane, reusedAsSetIn, Desperate Housewives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reusedAsSetIn Context triple: [1313 Mockingbird Lane, reusedAsSetIn, Desperate Housewives]
-
A.
reusedIn
chosen
Indicates that something previously used in one context or instance is used again in another context or instance.
-
B.
isReuseOf
Indicates that one entity is derived from, or created by reusing, the content, structure, or components of another entity.
-
C.
setsIn
Indicates that one entity places or positions another entity into or within a specified container, location, or context.
-
D.
partiallyReusedAs
Indicates that one entity is used again as part of another entity, but only to a limited or incomplete extent rather than in its entirety.
-
E.
collectivelySet
Indicates that multiple entities jointly determine or assign a value, state, or configuration together as a group rather than individually.
- 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_69f349436ee88190b72ee12d0f3f508e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:18 a.m.