Triple
T25215292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irie Jones |
E631810
|
entity |
| Predicate | setInWorkCountry |
P131264
|
FINISHED |
| Object | United Kingdom |
—
|
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: United Kingdom | Statement: [Irie Jones, setInWorkCountry, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setInWorkCountry Context triple: [Irie Jones, setInWorkCountry, United Kingdom]
-
A.
workFromCountry
Indicates that an entity performs their work or job while being physically located in a specified country.
-
B.
worksInCountry
chosen
Indicates that an entity performs its work or professional activities within the specified country.
-
C.
isSetInCountry
Indicates that something (such as an event, story, or scene) takes place within the geographical or political boundaries of a specified country.
-
D.
fromWorkCountryOfOrigin
Indicates that something originates from the same country as the subject’s place of work.
-
E.
setWorkIn
Indicates that an entity assigns or places a work, task, or project into a particular context, location, or setting.
- 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_69e75a8d1aa48190a4320acd3654762c |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f47b8bd25c819089de15eac12cd285 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 12:58 p.m.