Triple
T25149466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kristen Kish |
E630027
|
entity |
| Predicate | previousHostOf |
P46400
|
FINISHED |
| Object | Fast Foodies |
—
|
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: Fast Foodies | Statement: [Kristen Kish, previousHostOf, Fast Foodies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousHostOf Context triple: [Kristen Kish, previousHostOf, Fast Foodies]
-
A.
previousHostUnit
Indicates that an entity was formerly assigned to, located in, or associated with a specified host unit before its current one.
-
B.
hasFormerHost
chosen
Indicates that an entity previously served as the host of another entity but no longer holds that hosting role.
-
C.
previousHostCity
Indicates that one city served as the immediately preceding host city relative to another in a sequence of hosting events.
-
D.
originalHost
Indicates that one entity is the initial or primary host on which another entity first resided, originated, or was hosted.
-
E.
formerHostCountry
Indicates that one entity was previously the host country for another entity, but no longer holds that role.
- 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_69e2ff349e408190a6f4a5a66279f54d |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 18, 2026, 6:30 a.m.