Triple
T19445653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walter Hampden |
E486467
|
entity |
| Predicate | theatreSpecialization |
P16508
|
FINISHED |
| Object | classical theatre |
—
|
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: classical theatre | Statement: [Walter Hampden, theatreSpecialization, classical theatre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: theatreSpecialization Context triple: [Walter Hampden, theatreSpecialization, classical theatre]
-
A.
partOfTheatre
Indicates that one entity is a component, section, or subdivision of a theatre.
-
B.
theatre
Indicates that an entity is a theater or is associated with theatrical performances or activities.
-
C.
theatreType
chosen
Indicates the specific category or kind of theatre associated with an entity, such as its format, style, or operational model.
-
D.
theatreOf
Indicates that an event, action, or operation takes place within or is primarily associated with a particular theatre or venue.
-
E.
theatricalSubject
Indicates that an entity serves as the main focus, topic, or subject within a theatrical work, performance, or dramatic 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6338921cc819083f8f918225d78e6 |
completed | April 20, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.