Triple
T32060012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Travel Man |
E818721
|
entity |
| Predicate | hasOriginalHost |
P18035
|
FINISHED |
| Object | Richard Ayoade |
—
|
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: Richard Ayoade | Statement: [Travel Man, hasOriginalHost, Richard Ayoade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalHost Context triple: [Travel Man, hasOriginalHost, Richard Ayoade]
-
A.
originalHost
chosen
Indicates that one entity is the initial or primary host on which another entity first resided, originated, or was hosted.
-
B.
hasOriginalClient
Indicates that an entity is associated with the initial or primary client for whom it was originally created, configured, or served.
-
C.
hasOriginalLocation
Indicates that an entity was initially located or situated at a specified place or position before any change or movement occurred.
-
D.
hasFormerHost
Indicates that an entity previously served as the host of another entity but no longer holds that hosting role.
-
E.
hasOriginalVersion
Indicates that one entity is the original or initial version from which another entity is derived or adapted.
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
Created at: May 1, 2026, 12:21 a.m.