Triple
T37501490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edmonton, London, England |
E931973
|
entity |
| Predicate | hasLocalTheatre |
P102579
|
FINISHED |
| Object | Millfield 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: Millfield Theatre | Statement: [Edmonton, London, England, hasLocalTheatre, Millfield Theatre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalTheatre Context triple: [Edmonton, London, England, hasLocalTheatre, Millfield Theatre]
-
A.
hasMovieTheater
Indicates that one entity possesses, contains, or includes a movie theater as part of its facilities or attributes.
-
B.
hasMunicipalTheatre
chosen
Indicates that a place or administrative entity possesses or contains a municipal theatre as one of its facilities.
-
C.
hasNeighbouringTheatre
Indicates that one theatre is located close enough to another theatre to be considered its neighbor.
-
D.
hasTheatreDistrictRole
Indicates that an entity holds a specific role, function, or designation within a theatre district.
-
E.
isPartOfTheater
Indicates that one entity functions as a component, section, or subdivision within a larger theater (such as a theater building, complex, or organizational unit).
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff97637ad881908c24fe2cc6b036db |
completed | May 9, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69ff96c43a808190942eeda1934602db |
completed | May 9, 2026, 8:19 p.m. |
Created at: May 3, 2026, 4:17 p.m.