Triple
T14066383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyde Park on Hudson |
E338482
|
entity |
| Predicate | releaseEventDate |
P180
|
FINISHED |
| Object | September 2012 |
—
|
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: September 2012 | Statement: [Hyde Park on Hudson, releaseEventDate, September 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releaseEventDate Context triple: [Hyde Park on Hudson, releaseEventDate, September 2012]
-
A.
releasedDuring
Indicates that one entity was released within the time period defined by another entity.
-
B.
launchDate
chosen
Indicates the date on which an entity (such as a product, service, or project) is officially released or made available.
-
C.
rolloutDate
Indicates the date on which something (such as a product, feature, or policy) is first introduced or made available for general use.
-
D.
reReleaseDate
Indicates the date on which something is released again, such as a reissued or updated version of an existing item.
-
E.
announcementDate
Indicates the date on which an announcement is formally made or becomes publicly known.
- 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de568b81f08190a571004261c0e8e4 |
completed | April 14, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_69de05adef888190b023ab42ef5076b6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:21 p.m.