Triple
T11834639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taylor Report |
E281483
|
entity |
| Predicate | eventDateInvestigated |
P830
|
FINISHED |
| Object | 15 April 1989 |
—
|
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: 15 April 1989 | Statement: [Taylor Report, eventDateInvestigated, 15 April 1989]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventDateInvestigated Context triple: [Taylor Report, eventDateInvestigated, 15 April 1989]
-
A.
eventOccurredAt
Indicates that a particular event took place at a specific time or location.
-
B.
investigatedEvent
Indicates that an event was the subject of an investigation or inquiry carried out by some agent.
-
C.
investigatedAt
Indicates that an investigation into an entity or event took place at a specific location or facility.
-
D.
dateOfRelatedEvent
chosen
Indicates that there is a specific date on which a related event associated with the subject occurs or occurred.
-
E.
eventDateAtLocation
Indicates that a specific event occurs on a particular date at a given location.
- 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a62e7e408190998bebe346c82e89 |
completed | April 10, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_69d8a254a57481908a1e6ad97919c416 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.