Triple
T35354441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kate Armstrong |
E1020976
|
entity |
| Predicate | featuredInCastListOf |
P70373
|
FINISHED |
| Object | No Reservations |
E329479
|
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: No Reservations | Statement: [Kate Armstrong, featuredInCastListOf, No Reservations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredInCastListOf Context triple: [Kate Armstrong, featuredInCastListOf, No Reservations]
-
A.
featuresCast
chosen
Indicates that a creative work includes a particular person or group as part of its cast.
-
B.
includesCastMembersFrom
Indicates that one entity’s cast list contains one or more cast members who also appear in the cast list of another entity.
-
C.
mainCastIncludes
Indicates that a work’s primary cast features the specified person or character as one of its main members.
-
D.
laterFeaturedCastFrom
Indicates that one entity appears as a featured cast member in a later work, episode, or installment relative to another entity.
-
E.
joinsCastOf
Indicates that one entity becomes a member of the cast of another entity, such as an actor joining the cast of a show, film, or production.
- F. None of above.
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_69f76decd95c8190ae428f6a19d535de |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a384a1ce8488190bb80b9231523f08c |
completed | June 21, 2026, 8:31 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.