Triple
T14262846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DS512 |
E353567
|
entity |
| Predicate | panelEstablishedDate |
P113481
|
FINISHED |
| Object | 2017-02-22 |
—
|
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: 2017-02-22 | Statement: [DS512, panelEstablishedDate, 2017-02-22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: panelEstablishedDate Context triple: [DS512, panelEstablishedDate, 2017-02-22]
-
A.
establishedAt
Indicates the specific time or date at which something (such as an organization, system, or entity) was founded or brought into existence.
-
B.
establishedFrom
Indicates that something was created, founded, or formed starting from a specified source, origin, or prior entity.
-
C.
partnerStartDate
Indicates the date on which the partnership or partner relationship between the entities begins.
-
D.
placeEstablished
Indicates that an entity was founded, created, or formally established at a particular place or location.
-
E.
establishedTo
Indicates that one entity was created, founded, or set up for the purpose of serving, supporting, or enabling another entity.
- 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de63563fc88190b0abdbf8529c65eb |
completed | April 14, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69de2a7d586c8190846ff242bbf5ac53 |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:09 a.m.