Triple
T18916697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Jenkins |
E462741
|
entity |
| Predicate | historicityOfEarIncident |
P133778
|
FINISHED |
| Object | disputed by some historians |
—
|
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: disputed by some historians | Statement: [Robert Jenkins, historicityOfEarIncident, disputed by some historians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicityOfEarIncident Context triple: [Robert Jenkins, historicityOfEarIncident, disputed by some historians]
-
A.
hadEvent
Indicates that an entity experienced, hosted, or was associated with a specific event at some point in time.
-
B.
historicalEventWitnessed
Indicates that an entity personally observed or was present at a particular historical event.
-
C.
hadListeningEventAt
Indicates that a listening event involving an entity occurred at a specific time or place.
-
D.
hasHistoricalEvent
Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
-
E.
injuryOccurredAt
Indicates that an injury took place at a specific location or during a particular event or time.
- F. None of above. chosen
Provenance (4 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c627724881909cf63c67d64321e8 |
completed | April 20, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 11:58 a.m.