Triple
T34641338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Essex Regiment |
E889564
|
entity |
| Predicate | televisionPortrayalMedium |
P19219
|
FINISHED |
| Object | television drama |
—
|
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 drama | Statement: [South Essex Regiment, televisionPortrayalMedium, television drama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: televisionPortrayalMedium Context triple: [South Essex Regiment, televisionPortrayalMedium, television drama]
-
A.
televisionPortrayalCountry
Indicates the country in which a television portrayal of an entity is produced, set, or primarily associated.
-
B.
televisionShow
Indicates that one entity is a television show associated with, or featured in relation to, another entity.
-
C.
televisionShowDepicted
Indicates that one entity is a television show in which the other entity is portrayed, represented, or appears.
-
D.
televisionWork
chosen
Indicates a relationship where a creative work is produced for, broadcast on, or primarily associated with television.
-
E.
televisionUniverse
Indicates that two entities exist within the same fictional television continuity or shared TV universe.
- 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_69f349d724848190b63ad3407e0006d9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f728a345488190bd7e6751b09ac591 |
completed | May 3, 2026, 10:51 a.m. |
| PD | Predicate disambiguation | batch_69f7283ef2608190a7a85d7e7f5332c0 |
completed | May 3, 2026, 10:49 a.m. |
Created at: May 1, 2026, 2:04 a.m.