Triple
T26385499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Clay |
E663266
|
entity |
| Predicate | designedSetFor |
P9494
|
FINISHED |
| Object | Rent (Broadway production) |
—
|
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: Rent (Broadway production) | Statement: [Paul Clay, designedSetFor, Rent (Broadway production)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedSetFor Context triple: [Paul Clay, designedSetFor, Rent (Broadway production)]
-
A.
setsIn
Indicates that one entity places or positions another entity into or within a specified container, location, or context.
-
B.
isDesignedFor
chosen
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
-
C.
setsOut
Indicates that an entity begins a journey, course of action, or process, moving from an initial state or location toward a goal or destination.
-
D.
designedWith
Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
-
E.
setsOn
Indicates that one entity places or arranges another entity onto a specified surface, container, or context.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 26, 2026, 11:22 p.m.