Triple
T16369669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Orchid House |
E397530
|
entity |
| Predicate | firstPublicationYearApprox |
P49730
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [The Orchid House, firstPublicationYearApprox, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPublicationYearApprox Context triple: [The Orchid House, firstPublicationYearApprox, 2010]
-
A.
firstPublishedInWorkYear
Indicates the year in which a work was first published.
-
B.
firstCompletePublicationYear
Indicates the calendar year in which an entity’s first complete publication was released.
-
C.
firstAssociatedPublicationYear
Indicates the calendar year in which an entity’s earliest associated publication was first released or made publicly available.
-
D.
approximateStartYear
Indicates that the associated year value represents an estimated or imprecise starting year for an event, state, or relationship rather than an exact one.
-
E.
releaseApproximateYear
chosen
Indicates that an entity was released or made available around a specified year, where the year is approximate rather than exact.
- 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_69d87f2778dc8190aa95c7572db127e6 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2ff4021e88190ad093bab74cf82a4 |
completed | April 18, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69e226f37ecc819082af58b29b4e39d1 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.