Triple
T35365896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bill (2015 film) |
E1021626
|
entity |
| Predicate | featuresCreativeTeamFrom |
P206954
|
FINISHED |
| Object | Horrible Histories |
E1021622
|
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: Horrible Histories | Statement: [Bill (2015 film), featuresCreativeTeamFrom, Horrible Histories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresCreativeTeamFrom Context triple: [Bill (2015 film), featuresCreativeTeamFrom, Horrible Histories]
-
A.
creativeTeamMember
Indicates that an entity participates as a member of a team responsible for creative work or production.
-
B.
featuresTeamUp
Indicates that two or more entities collaborate or join forces to act together as a team.
-
C.
designTeamFrom
Indicates that a design team originates from, is based in, or is associated with a specified source entity or location.
-
D.
featuredTeam
Indicates that a particular team is highlighted or given special prominence in a given context or presentation.
-
E.
featureCrew
Indicates that a particular crew member is highlighted or designated as a featured participant within a crew-related context.
- F. None of above. chosen
Provenance (5 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_69f76df000488190ab7c97f565677055 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a382cb38b3c8190b977b2a7b974aaf9 |
completed | June 21, 2026, 6:25 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.