Triple
T30651976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Assembled Parties (Broadway production) |
E780282
|
entity |
| Predicate | extendedRun |
P34500
|
FINISHED |
| Object | true |
—
|
LITERAL FINISHED |
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: true | Statement: [The Assembled Parties (Broadway production), extendedRun, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extendedRun Context triple: [The Assembled Parties (Broadway production), extendedRun, true]
-
A.
extendedIn
Indicates that one entity continues, prolongs, or expands the scope, duration, or range of another entity.
-
B.
extendedFor
Indicates that something has been lengthened in duration, scope, or extent specifically for the benefit or use of another entity.
-
C.
extendedIndefinitelyOn
Indicates that something was prolonged or continued without a specified end point in relation to something else.
-
D.
extendedPractice
Indicates that an entity engages in a prolonged or repeated practice or rehearsal of an activity beyond its usual or standard duration.
-
E.
extendedOn
chosen
Indicates that one entity continues, prolongs, or expands the duration, scope, or effect of another entity beyond its original limit.
- 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_69f224a5d2b481908a6853cd0138e2d7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a98249081909b4be467f5a37110 |
completed | May 2, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:30 p.m.