Triple
T30810981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Reynolds |
E784643
|
entity |
| Predicate | dateOfHamptonCourtConferenceContribution |
P6885
|
FINISHED |
| Object | 1604 |
—
|
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: 1604 | Statement: [John Reynolds, dateOfHamptonCourtConferenceContribution, 1604]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfHamptonCourtConferenceContribution Context triple: [John Reynolds, dateOfHamptonCourtConferenceContribution, 1604]
-
A.
yearOfCouncilReferenced
Indicates that one entity specifies or cites the calendar year in which a particular council took place.
-
B.
convenedOn
chosen
Indicates that an event, meeting, or formal gathering took place or was held on a specific date or time.
-
C.
conferenceDatesSpecified
Indicates that the specific dates on which the conference will take place have been defined and recorded.
-
D.
conductedOn
Indicates that an action, process, or event was carried out with respect to, or took place on, a specified subject, object, or medium.
-
E.
councilHeldBetween
Indicates that a council, meeting, or formal deliberative session was held involving the two specified entities as participating parties.
- 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_69f224b4eda48190bd212ce4f3901e56 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: April 29, 2026, 8:43 p.m.