Triple
T25558118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saxon Shore Way |
E640629
|
entity |
| Predicate | followsHistoricalFeature |
P165820
|
FINISHED |
| Object | Saxon Shore |
—
|
NE NERFINISHED |
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: Saxon Shore | Statement: [Saxon Shore Way, followsHistoricalFeature, Saxon Shore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsHistoricalFeature Context triple: [Saxon Shore Way, followsHistoricalFeature, Saxon Shore]
-
A.
hasHistoricFeatures
Indicates that something possesses characteristics, elements, or attributes of historical significance.
-
B.
featuresHistorian
Indicates that something includes or presents a historian as a notable participant, subject, or element.
-
C.
hasHistoricity
Indicates that something possesses historical existence, significance, or authenticity, rather than being purely fictional, mythical, or timeless.
-
D.
historicalFunction
Indicates the role, purpose, or activity an entity had during a past period or in a historical context.
-
E.
historicalPattern
Indicates a recurring relationship or sequence of events between entities that has been observed over 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_69e75dc1beb08190bac7d76b8d6e7bc4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65a9cb0bc8190bf8a9b319900bad5 |
completed | May 2, 2026, 8:12 p.m. |
Created at: April 21, 2026, 3:44 p.m.