Triple
T5756286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woolwich Ferry |
E126975
|
entity |
| Predicate | openedAsFreeServiceYear |
P66202
|
FINISHED |
| Object | 1889 |
—
|
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: 1889 | Statement: [Woolwich Ferry, openedAsFreeServiceYear, 1889]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsFreeServiceYear Context triple: [Woolwich Ferry, openedAsFreeServiceYear, 1889]
-
A.
openedForCommercialService
Indicates that something (such as a facility, route, or service) began operating and became available for regular commercial use.
-
B.
officialOpeningYear
Indicates the calendar year in which something was formally opened or inaugurated for official use.
-
C.
openedAt
Indicates that an entity began operating, became accessible, or was first made available at a specific time or date.
-
D.
beganInYear
Indicates that an event, process, or state started in a specific calendar year.
-
E.
firstYearOfUse
Indicates the year in which something was first put into use or began being used.
- 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_69c00832aedc81909899801b141fa3b4 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02906848c8190bf7b0d62f57c27fa |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021cc68648190bb86d049ebe80f12 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c028fec2bc819083f5dca6a8d9d435 |
completed | March 22, 2026, 5:38 p.m. |
Created at: March 22, 2026, 3:49 p.m.