Triple
T35919243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 34 St–Herald Sq |
E1038833
|
entity |
| Predicate | originalINDOpeningDate |
P206108
|
FINISHED |
| Object | 1940 |
—
|
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: 1940 | Statement: [34 St–Herald Sq, originalINDOpeningDate, 1940]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalINDOpeningDate Context triple: [34 St–Herald Sq, originalINDOpeningDate, 1940]
-
A.
officialOpeningDate
Indicates the calendar date on which something is formally inaugurated or officially opened for use or operation.
-
B.
firstLineOpeningDate
Indicates the date on which the first line in a system, network, or service was officially opened or began operation.
-
C.
rerAOpeningDate
Indicates the date on which something (such as a facility, service, or route) is opened again after having been closed.
-
D.
firstLocationOpeningDate
Indicates the date on which the first location associated with the subject entity was opened.
-
E.
openingDay
Indicates the specific day on which something, typically an event, season, or venue, officially begins or first opens to the public.
- 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_69f76e2320748190b7f5c4750d0cd0d3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037ce53de881908cf14141cf3bc570 |
completed | May 12, 2026, 7:17 p.m. |
Created at: May 3, 2026, 4:07 p.m.