Triple
T24230695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whose Line Is It Anyway? (U.S. version) |
E601722
|
entity |
| Predicate | hostEra |
P155282
|
FINISHED |
| Object | Drew Carey era |
—
|
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: Drew Carey era | Statement: [Whose Line Is It Anyway? (U.S. version), hostEra, Drew Carey era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostEra Context triple: [Whose Line Is It Anyway? (U.S. version), hostEra, Drew Carey era]
-
A.
homeEra
Indicates the historical period or era in which something is primarily based, originates, or is most characteristically situated.
-
B.
host
Indicates that one entity provides space, resources, or services to accommodate, receive, or entertain another entity.
-
C.
hostArena
Indicates that one entity serves as the arena or venue where an event or activity involving the other entity takes place.
-
D.
hostEmpire
Indicates that one entity serves as the imperial authority or ruling empire that hosts, controls, or encompasses another entity.
-
E.
hostMonarch
Indicates that one entity serves as the reigning monarch or royal ruler presiding over another entity (such as a realm, territory, or people).
- 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_69e29538aafc8190a2386fdebbd1393b |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f287e3187c8190ab054ad983ed0335 |
completed | April 29, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 18, 2026, 12:01 a.m.