Triple
T34559878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lisa Bowerman |
E887306
|
entity |
| Predicate | worksInFranchise |
P39171
|
FINISHED |
| Object | Doctor Who expanded universe |
—
|
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: Doctor Who expanded universe | Statement: [Lisa Bowerman, worksInFranchise, Doctor Who expanded universe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksInFranchise Context triple: [Lisa Bowerman, worksInFranchise, Doctor Who expanded universe]
-
A.
includedInFranchise
Indicates that an entity is part of, or belongs to, a larger franchise or franchise series.
-
B.
franchiseWorkedOn
chosen
Indicates that an entity has contributed work to, or been professionally involved with, a particular franchise.
-
C.
hasItemInFranchise
Indicates that an entity possesses or includes a specific item as part of a larger franchise or branded collection.
-
D.
usedByFranchise
Indicates that something (such as a resource, asset, or element) is utilized or employed by a particular franchise.
-
E.
partOfFranchiseLineage
Indicates that one entity belongs to, or is derived from, the same overarching franchise lineage as another entity, reflecting continuity within a shared franchise.
- 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_69f349d0c4d881908dd0950f5eb9ec0a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 1, 2026, 2:02 a.m.