Triple
T24978656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glover’s Rock |
E625099
|
entity |
| Predicate | eventDateReferenced |
P830
|
FINISHED |
| Object | October 18, 1776 |
—
|
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: October 18, 1776 | Statement: [Glover’s Rock, eventDateReferenced, October 18, 1776]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventDateReferenced Context triple: [Glover’s Rock, eventDateReferenced, October 18, 1776]
-
A.
eventDateContext
Indicates the contextual role or significance that a specific date has within an event (e.g., whether it is the start, end, deadline, or another relevant temporal marker).
-
B.
eventDateReviewed
Indicates the date on which an event was examined, checked, or formally reviewed.
-
C.
eventDateAtLocation
Indicates that a specific event occurs on a particular date at a given location.
-
D.
capitalEventDate
Indicates the date on which a capital-related event (such as establishment, designation, or change of capital status) occurred.
-
E.
dateOfRelatedEvent
chosen
Indicates that there is a specific date on which a related event associated with the subject occurs or occurred.
- 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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f449045fc0819094f70ddb8fd4ae75 |
completed | May 1, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:02 a.m.