Triple
T10294646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GYE |
E241450
|
entity |
| Predicate | openedInCurrentForm |
P763
|
FINISHED |
| Object | 2006 |
—
|
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: 2006 | Statement: [GYE, openedInCurrentForm, 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedInCurrentForm Context triple: [GYE, openedInCurrentForm, 2006]
-
A.
establishedInCurrentForm
chosen
Indicates the point in time when something took on its present structure, organization, or configuration, distinct from any earlier versions or forms.
-
B.
openedIn
Indicates that an entity (such as a business, event, or institution) began operating or was inaugurated in a specific time period or location.
-
C.
openedAs
Indicates that one entity began operating, functioning, or being available to the public under the form, name, or role of another entity.
-
D.
establishedInCurrentFormBy
Indicates that one entity created, organized, or defined another entity in the specific structure or configuration in which it currently exists.
-
E.
currentForm
Indicates the present or most recently adopted version, shape, or state that something currently has.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2d5e0f88190be3e23ba2511a1e9 |
completed | April 7, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f35e548190be3b4d92d65d2d20 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:42 a.m.