Triple
T12705894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Mary the Virgin Church, Turville |
E303583
|
entity |
| Predicate | usedInProduction |
P89107
|
FINISHED |
| Object | television series |
—
|
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: television series | Statement: [St Mary the Virgin Church, Turville, usedInProduction, television series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInProduction Context triple: [St Mary the Virgin Church, Turville, usedInProduction, television series]
-
A.
hasProductionUse
chosen
Indicates that something is utilized or applied within a production or operational environment.
-
B.
usesProductionModel
Indicates that one entity employs or relies on another entity as its primary or official production model in practice.
-
C.
performedInProduction
Indicates that an entity (such as a person or group) took part as a performer in a specific production or performance event.
-
D.
usedInPractice
Indicates that something is actually applied or implemented in real-world practice rather than just being theoretical or proposed.
-
E.
usedInProject
Indicates that something (such as a resource, tool, or component) is employed or utilized within a particular project.
- 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_69d7bdef90d48190b46b88270e780946 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961f1adec8190a53c80e9556b3fe0 |
completed | April 10, 2026, 8:47 p.m. |
| PD | Predicate disambiguation | batch_69d960c088dc8190b0e63312c54e4c6c |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:23 p.m.