Triple
T25898642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Admiral’s Men |
E652540
|
entity |
| Predicate | laterMainVenue |
P85539
|
FINISHED |
| Object | The Fortune Theatre |
E389742
|
NE 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: The Fortune Theatre | Statement: [Lord Admiral’s Men, laterMainVenue, The Fortune Theatre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterMainVenue Context triple: [Lord Admiral’s Men, laterMainVenue, The Fortune Theatre]
-
A.
laterPerformanceVenue
chosen
Indicates that a performance or event took place at this venue at a later time than another referenced performance or venue.
-
B.
previousVenue
Indicates that one venue was used or occupied before another in a sequence of venues.
-
C.
earlyVenue
Indicates that an event or activity takes place at a venue earlier than a standard, expected, or comparative time.
-
D.
formerVenueComponentOf
Indicates that a venue previously functioned as a component or part of a larger venue or venue complex, but no longer holds that status.
-
E.
isCentralVenueOf
Indicates that a venue serves as the primary or main location for a specified event, organization, or activity.
- F. None of above.
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_69e7ab3c6cc081908de59bfcc28ec19d |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a11273090bc8190b1067ade0eedca9b |
completed | May 23, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 22, 2026, 8:23 a.m.