Triple
T18222215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tidyr |
E436332
|
entity |
| Predicate | firstReleaseApproxYear |
P56255
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [tidyr, firstReleaseApproxYear, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstReleaseApproxYear Context triple: [tidyr, firstReleaseApproxYear, 2014]
-
A.
initialReleaseApprox
chosen
Indicates that an entity’s first release or debut occurred around an estimated or approximate point in time rather than on a precisely known date.
-
B.
firstVersionYear
Indicates the calendar year in which the first version or initial release of something was created, published, or made available.
-
C.
firstCommercialReleaseYear
Indicates the calendar year in which something (such as a product, work, or service) was first made commercially available to the public.
-
D.
releaseApproximateYear
Indicates that an entity was released or made available around a specified year, where the year is approximate rather than exact.
-
E.
firstCreationYear
Indicates the year in which something was first created or originally produced.
- 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_69d8b9103a8081908bbb0836fef10efd |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e47c85108190bd9707b40bdfdb38 |
completed | April 19, 2026, 2:19 p.m. |
| PD | Predicate disambiguation | batch_69e4332336cc8190808b9c70c888ba65 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:32 a.m.