Triple
T15277808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colin Morris-Jones |
E365187
|
entity |
| Predicate | setWithinEvent |
P2808
|
FINISHED |
| Object | HIV/AIDS epidemic in the United Kingdom |
—
|
LITERAL FINISHED |
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: HIV/AIDS epidemic in the United Kingdom | Statement: [Colin Morris-Jones, setWithinEvent, HIV/AIDS epidemic in the United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setWithinEvent Context triple: [Colin Morris-Jones, setWithinEvent, HIV/AIDS epidemic in the United Kingdom]
-
A.
setInEvent
chosen
Indicates that an entity is situated within, occurs during, or is contextually located in a particular event.
-
B.
setAgainstEvent
Indicates that one event is positioned or framed in opposition or contrast to another event.
-
C.
regionDuringEvent
Indicates that a specified region is associated with or exists within the spatial scope of a particular event during its occurrence.
-
D.
posedAtEvent
Indicates that an entity assumed a particular pose or posture during a specified event.
-
E.
appliedInEvent
Indicates that an action, method, or concept is utilized or carried out within the context of a specific event.
- 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_69d85a103d9081908c1ea6c4c73ac8e3 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00953bc848190b83919f39d5ee37b |
completed | April 15, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69deca90739081909bd1b797cdb8af2b |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:14 a.m.