Triple
T3396306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waterfront station |
E71536
|
entity |
| Predicate | formerNameInUseUntil |
P25649
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Waterfront station, formerNameInUseUntil, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerNameInUseUntil Context triple: [Waterfront station, formerNameInUseUntil, 2011]
-
A.
formerName
Indicates that an entity was previously known by a different name in the past.
-
B.
previousNameUsedUntil
chosen
Indicates that a particular name was used for an entity up to (but not necessarily including) a specified end date or time.
-
C.
operatedAsNameUntil
Indicates that an entity functioned or was known under a particular name up to a specified point in time.
-
D.
formerMemberName
Indicates that the referenced name belongs to an entity that was previously a member of a particular group, organization, or body but is no longer one.
-
E.
formerNamePeriodStart
Indicates the date or time point when an entity began using a former name that is being recorded.
- 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_69ad85a9c4a88190a854019341cb3b60 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb856158c81908dd7d3f1f8d6af74 |
completed | March 8, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69adadf705608190975423779430cc58 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:14 p.m.