Triple
T24779306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ravenglass and Eskdale Railway |
E619947
|
entity |
| Predicate | originalOpeningPurpose |
P96898
|
FINISHED |
| Object | carrying iron ore |
—
|
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: carrying iron ore | Statement: [Ravenglass and Eskdale Railway, originalOpeningPurpose, carrying iron ore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalOpeningPurpose Context triple: [Ravenglass and Eskdale Railway, originalOpeningPurpose, carrying iron ore]
-
A.
openingMotive
Indicates the initial reason, trigger, or intent that prompts an action or event to begin.
-
B.
originalOpeningAs
Indicates that one entity serves as the initial or first version of another entity’s opening or beginning.
-
C.
initialOpening
Indicates the first or earliest instance in which something is opened, begun, or made accessible.
-
D.
originalOpeningSection
Indicates that one section is the initial or first opening section of another work, document, or structured content.
-
E.
intendedOpeningUse
chosen
Indicates that an opening (such as a door, window, or passage) is designed or meant to be used for a particular purpose or function.
- 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 18, 2026, 4:43 a.m.