Triple
T468677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Library Theatre Company |
E8505
|
entity |
| Predicate | hasProgrammeType |
P2192
|
FINISHED |
| Object | in-house productions |
—
|
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: in-house productions | Statement: [Library Theatre Company, hasProgrammeType, in-house productions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProgrammeType Context triple: [Library Theatre Company, hasProgrammeType, in-house productions]
-
A.
hasProgramme
Indicates that an entity is associated with or offers a particular programme (such as a course of study, plan, or structured set of activities).
-
B.
hasGlobalProgramme
Indicates that an entity operates, participates in, or is associated with a programme that is implemented or recognized at a global or international level.
-
C.
programType
chosen
Indicates the category or kind of program to which an entity belongs or with which it is associated.
-
D.
hasProjectType
Indicates that an entity is associated with, or classified under, a specific type or category of project.
-
E.
hasServiceType
Indicates that an entity is associated with or categorized by a particular type of service.
- 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_69a2e7f3aeb48190a19453e3a043f486 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efee0ea0819099d87f3727c03bc7 |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2edebb3988190907992a584b4e260 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.