Triple
T28443841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Your Face or Mine? |
E715782
|
entity |
| Predicate | coHostInRevival |
P66215
|
FINISHED |
| Object | Katherine Ryan |
—
|
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: Katherine Ryan | Statement: [Your Face or Mine?, coHostInRevival, Katherine Ryan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coHostInRevival Context triple: [Your Face or Mine?, coHostInRevival, Katherine Ryan]
-
A.
revivalHost
Indicates that one entity serves as the host or venue where a revival event, such as a renewed performance, series, or movement, takes place.
-
B.
revivalPlatform
Indicates that an entity serves as the medium, venue, or system through which another entity is brought back, renewed, or reintroduced after a period of decline or inactivity.
-
C.
originalCoHost
chosen
Indicates that an entity served as an initial or first co-host alongside another entity in a shared hosting role.
-
D.
notableRevivalHost
Indicates that an entity served as a prominent or distinguished host for a revival or renewed version of another entity (such as a show, event, or series).
-
E.
2009RevivalHost
Indicates that the subject hosted the 2009 revival of a particular show, event, or series.
- 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_69efd6b44550819094ae991b553d9fc3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f64e405aa881909b1c15c7cf46b4d4 |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 1:47 a.m.