Triple
T7574475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westar 6 |
E179326
|
entity |
| Predicate | retrievalDate |
P77546
|
FINISHED |
| Object | 1984-11-14 |
—
|
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-11-14 | Statement: [Westar 6, retrievalDate, 1984-11-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retrievalDate Context triple: [Westar 6, retrievalDate, 1984-11-14]
-
A.
acquisitionDate
Indicates the date on which one entity formally acquires or takes ownership of another entity.
-
B.
cataloguedDate
Indicates the date on which an item or entity was formally recorded or entered into a catalog or database.
-
C.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
D.
dateReceived
Indicates the point in time when something (such as a message, item, or document) was received by a recipient.
-
E.
accessionDate
Indicates the date on which an item, record, or entity was formally added to a collection, system, or repository.
- 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_69c69f316e50819081a271c85c06f918 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f948e1e08190ad807292365a0c27 |
completed | March 27, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69c6f4de77048190b8769e717fdcf8e7 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f5b1a6a08190b9ff2bc8a7befe0d |
completed | March 27, 2026, 9:25 p.m. |
Created at: March 27, 2026, 3:51 p.m.