Triple
T12678200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Man’s Creek |
E302874
|
entity |
| Predicate | dateOfHistoricalAssociation |
P106239
|
FINISHED |
| Object | 1832 |
—
|
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: 1832 | Statement: [Old Man’s Creek, dateOfHistoricalAssociation, 1832]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfHistoricalAssociation Context triple: [Old Man’s Creek, dateOfHistoricalAssociation, 1832]
-
A.
hasHistoricSignificanceFor
Indicates that something holds notable historical importance or relevance for a particular entity or group.
-
B.
historicallyLinked
Indicates that two entities are connected through a shared or related historical event, period, or development.
-
C.
historicalRegionAssociation
Indicates an association where an entity is or was located in, part of, or otherwise related to a specific historical region.
-
D.
dateOfNationalMonumentDesignation
Indicates the specific date on which something was officially designated as a national monument.
-
E.
hasNotableHistoricalAssociation
Indicates that there is a significant connection between an entity and an important historical event, figure, period, or development.
- 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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961b1dff48190923290555ece5d89 |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960bb64ec8190bd0400cf0cc8b0a7 |
completed | April 10, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69d961acadb8819098de743bc951fedb |
completed | April 10, 2026, 8:46 p.m. |
Created at: April 9, 2026, 5:20 p.m.