Triple
T36351992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Garrison Pub |
E895229
|
entity |
| Predicate | controlledByInSeries |
P198933
|
FINISHED |
| Object | Thomas Shelby |
—
|
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: Thomas Shelby | Statement: [The Garrison Pub, controlledByInSeries, Thomas Shelby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlledByInSeries Context triple: [The Garrison Pub, controlledByInSeries, Thomas Shelby]
-
A.
operatesInSeries
Indicates that one entity functions or is used sequentially with another entity as part of a series configuration or process.
-
B.
usedInSeries
Indicates that something (such as an element, component, or concept) is employed or appears within a particular series.
-
C.
isSeriesOf
Indicates that one entity is a sequence or set of related items that collectively form a series associated with another entity.
-
D.
basedInSeriesSetting
Indicates that something (such as a work, event, or element) is situated within or occurs in the primary setting established by a particular series.
-
E.
diesInSeries
Indicates that the entity (typically a character) dies at some point within the specified series.
- 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_69f76e4f437c8190a1af3ea2564f41f5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff14d596e88190be5263b7f96a96cd |
completed | May 9, 2026, 11:04 a.m. |
| PD | Predicate disambiguation | batch_69ff13f0208081909369aeb3b77a6b1f |
completed | May 9, 2026, 11:01 a.m. |
| PDg | Predicate description generation | batch_69ff14d4dfc48190bc9fba2384988a98 |
completed | May 9, 2026, 11:04 a.m. |
Created at: May 3, 2026, 4:09 p.m.