Triple
T31243625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brother Michael |
E796627
|
entity |
| Predicate | countryOfOriginOfWorkMention |
P129719
|
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: [Brother Michael, countryOfOriginOfWorkMention, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryOfOriginOfWorkMention Context triple: [Brother Michael, countryOfOriginOfWorkMention, United Kingdom]
-
A.
placeOfOriginOfWork
Indicates the location where a work (such as an artwork, literary piece, or other creation) was originally produced or created.
-
B.
associatedWorkCountryOfOrigin
chosen
Indicates that the related work originates from, or is primarily associated with, a specified country.
-
C.
workOriginatesFrom
Indicates that the creation, development, or initiation of a work can be traced back to a particular source, agent, or origin.
-
D.
organizationCountryOfOrigin
Indicates the country where an organization was originally founded or established.
-
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_69f224dc84d0819081f1cb6f9127e6b1 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ffdf47d9608190830ca23d9cef6409 |
completed | May 10, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69ffdf00e2b4819082dd5cb78f316baf |
completed | May 10, 2026, 1:27 a.m. |
Created at: April 29, 2026, 9:11 p.m.