Triple
T27491377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shakespearean theatre district of Bankside |
E693892
|
entity |
| Predicate | hadPlayhouse |
P162447
|
FINISHED |
| Object | the Globe Theatre |
—
|
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: the Globe Theatre | Statement: [Shakespearean theatre district of Bankside, hadPlayhouse, the Globe Theatre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadPlayhouse Context triple: [Shakespearean theatre district of Bankside, hadPlayhouse, the Globe Theatre]
-
A.
laterPrimaryPlayhouse
Indicates that the referenced playhouse served as the primary venue for a subject at a later period, following an earlier main playhouse.
-
B.
hadMeetingHouse
Indicates that an entity possessed or was associated with a specific meeting house as a place for gatherings or assemblies.
-
C.
closedAsPlayhouse
Indicates that a venue or building ceased operations specifically in its function as a playhouse or theater.
-
D.
hasPavilion
Indicates that one entity possesses, includes, or is associated with a pavilion as part of its structure, property, or facilities.
-
E.
hadWorkhouse
Indicates that an entity possessed, operated, or was associated with a workhouse.
- 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_69ef5382b9648190be0b1ef2ad5d043c |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62e8941e081908e2b8e35bd5461cb |
completed | May 2, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f624c006788190a2f4d5015c96463f |
completed | May 2, 2026, 4:22 p.m. |
Created at: April 27, 2026, 1:05 p.m.