Triple
T588609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harold Prince Theatre |
E17215
|
entity |
| Predicate | dedicatedToField |
P3164
|
FINISHED |
| Object | performing arts |
—
|
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: performing arts | Statement: [Harold Prince Theatre, dedicatedToField, performing arts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dedicatedToField Context triple: [Harold Prince Theatre, dedicatedToField, performing arts]
-
A.
dedicated
Indicates that one entity is formally assigned, reserved, or committed for the specific use, benefit, or purpose of another entity.
-
B.
rededicatedBy
Indicates that something has been dedicated again or anew by a particular agent or entity.
-
C.
relatedField
Indicates that one field, topic, or area of study is connected or relevant to another in subject matter or application.
-
D.
dedicationDate
Indicates the date on which something (such as a building, monument, or work) is formally dedicated or inaugurated.
-
E.
servesField
chosen
Indicates that one entity performs a service or function specifically for, or in support of, a particular field, domain, or area of activity.
- 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_69a49379d09c8190ac7e00b24e2810b1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49b9d1e68819096a9b5e7b2e83d6e |
completed | March 1, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69a494ca68448190a516b9c3525d8916 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.