Triple
T31958475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Ryan |
E815970
|
entity |
| Predicate | eventPrimaryLocation |
P147149
|
FINISHED |
| Object | Hungerford, Berkshire, England |
—
|
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: Hungerford, Berkshire, England | Statement: [Michael Ryan, eventPrimaryLocation, Hungerford, Berkshire, England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventPrimaryLocation Context triple: [Michael Ryan, eventPrimaryLocation, Hungerford, Berkshire, England]
-
A.
eventLocationDetail
Indicates the specific place or venue where an event occurs, often providing more granular location information than a general address or area.
-
B.
locationOfEventOrganized
chosen
Indicates the place where a particular organized event is held or takes place.
-
C.
eventLocationOfNotableActivity
Indicates that a location is the place where a notable or significant activity or event involving the related entity occurred.
-
D.
locationOfEventDescribed
Indicates that one entity is the place or setting where the event described by another entity occurs.
-
E.
locationOfEventSeries
Indicates the place or setting where a recurring or related series of events takes place.
- 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 12:08 a.m.