Triple
T3202290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J.B. |
E67077
|
entity |
| Predicate | notableProductionType |
P46117
|
FINISHED |
| Object | Broadway production |
—
|
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: Broadway production | Statement: [J.B., notableProductionType, Broadway production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableProductionType Context triple: [J.B., notableProductionType, Broadway production]
-
A.
notableTelevisionProduction
Indicates that the subject is significantly associated with the creation or production of the referenced television work.
-
B.
notableProgramType
Indicates that the subject is recognized for or associated with a particular type or category of program.
-
C.
notableProductType
Indicates that an entity is particularly well-known or distinguished for producing or offering a specific type of product.
-
D.
producedFilmType
Indicates that an entity (such as a person or organization) was responsible for producing a film of a specified type or category.
-
E.
notableShowProduced
Indicates that an entity played a significant role in producing a show that is considered notable.
- 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_69ad8589bd988190afa7ed2bdffb7b33 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada9b046c8819087c0a61c4f9adeb7 |
completed | March 8, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69ad9e078f7c8190813d9fcb4f5071fb |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f9259c8190afbc5ad0fa55436b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:07 p.m.