Triple
T29065235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greenhow |
E735654
|
entity |
| Predicate | historicRiding |
P65445
|
FINISHED |
| Object | West Riding of Yorkshire |
—
|
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: West Riding of Yorkshire | Statement: [Greenhow, historicRiding, West Riding of Yorkshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicRiding Context triple: [Greenhow, historicRiding, West Riding of Yorkshire]
-
A.
historicalRiding
Indicates a relationship where one entity rode or traveled on another entity in the past.
-
B.
historicRoute
Indicates that a route has historical significance, typically due to its age, past usage, or role in notable events.
-
C.
historicFor
chosen
Indicates that something holds historical significance or importance specifically in relation to another entity.
-
D.
otherHistoricSee
Indicates that an entity is associated with or linked to another historically significant site, event, or point of interest that can be seen or visited.
-
E.
historicAlly
Indicates that one entity has supported, allied with, or been favorably associated with another over a significant period in the past.
- 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_69f077e85498819088b65186550da8cd |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fe6e492bf8819080b25221d13445ea |
completed | May 8, 2026, 11:14 p.m. |
| PD | Predicate disambiguation | batch_69fe6dd33a6881908fe9bbbc184cab51 |
completed | May 8, 2026, 11:12 p.m. |
Created at: April 28, 2026, 10:17 a.m.