Triple
T33446913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roger Button |
E856530
|
entity |
| Predicate | hasAuthorialCountryOfOrigin |
P6689
|
FINISHED |
| Object | United States |
—
|
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 States | Statement: [Roger Button, hasAuthorialCountryOfOrigin, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuthorialCountryOfOrigin Context triple: [Roger Button, hasAuthorialCountryOfOrigin, United States]
-
A.
writtenInCountry
Indicates that a written work was created, authored, or composed within the geographical boundaries of a specific country.
-
B.
literaryOriginCountry
Indicates the country from which a literary work or literary tradition originally comes.
-
C.
countryOfManuscript
Indicates the country with which a manuscript is associated, typically where it was created, found, or is held.
-
D.
authorNationality
chosen
Indicates the relationship between an author and the country or nationality with which that author is identified.
-
E.
countryOfNotableWork
Indicates the country with which a notable work is primarily associated, such as where it was created, set, or gained its significance.
- 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_69f34971b75881908be360bb041f003c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: May 1, 2026, 1:37 a.m.