Triple
T3277025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stockton and Darlington Railway |
E68780
|
entity |
| Predicate | hasAnniversary |
P6046
|
FINISHED |
| Object | bicentenary in 2025 |
—
|
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: bicentenary in 2025 | Statement: [Stockton and Darlington Railway, hasAnniversary, bicentenary in 2025]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAnniversary Context triple: [Stockton and Darlington Railway, hasAnniversary, bicentenary in 2025]
-
A.
anniversaryNumber
Indicates the specific ordinal count of an anniversary occurrence in a recurring commemorative event or relationship.
-
B.
signedOnAnniversaryOf
Indicates that an agreement or document was signed on the anniversary date of a specific prior event or reference point.
-
C.
typeOfAnniversary
chosen
Indicates the specific category or kind of anniversary that an event or date represents (e.g., wedding, work, founding).
-
D.
hasBirthday
Indicates that an entity has a specific date on which its birth or founding is celebrated.
-
E.
completionAnniversary
Indicates the date or event marking the anniversary of when something was originally completed.
- 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_69ad859b54f881909bf530d549caf2fd |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0128f08819084644f3c8fda2596 |
completed | March 8, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69ada420167c81909b6e2702db296d9e |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.