Triple
T15362980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forest Park branch |
E367335
|
entity |
| Predicate | openedAsCurrentConfiguration |
P28427
|
FINISHED |
| Object | 1984 |
—
|
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: 1984 | Statement: [Forest Park branch, openedAsCurrentConfiguration, 1984]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsCurrentConfiguration Context triple: [Forest Park branch, openedAsCurrentConfiguration, 1984]
-
A.
openedAsCurrentAlignment
Indicates that one entity was opened or initiated in the same configuration, position, or state as the current alignment of another entity.
-
B.
openedAs
Indicates that one entity began operating, functioning, or being available to the public under the form, name, or role of another entity.
-
C.
openedAsCurrentLineNumber
Indicates that an item was opened or accessed when it was at the specified current line number in a sequence or document.
-
D.
openedAsCurrentBuilding
chosen
Indicates that an entity began operating or was inaugurated in its current building or physical premises.
-
E.
openedIn
Indicates that an entity (such as a business, event, or institution) began operating or was inaugurated in a specific time period or location.
- 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_69d85a1483788190ad93c2748e8af34b |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e479f188190bbbc3dcd73853e02 |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69deca991e5081908b0df3d1ee7d5338 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:18 a.m.