Triple
T28818516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giardia |
E727694
|
entity |
| Predicate | discoveryYearApproximate |
P139680
|
FINISHED |
| Object | 1681 |
—
|
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: 1681 | Statement: [Giardia, discoveryYearApproximate, 1681]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveryYearApproximate Context triple: [Giardia, discoveryYearApproximate, 1681]
-
A.
discoveryYear_approx
chosen
Indicates that the year associated with a discovery is known only approximately rather than as an exact calendar year.
-
B.
discoveryYear
Indicates the calendar year in which something was first discovered or identified.
-
C.
releaseApproximateYear
Indicates that an entity was released or made available around a specified year, where the year is approximate rather than exact.
-
D.
approximatePremiereYear
Indicates the estimated calendar year in which something, typically a work or event, first premiered.
-
E.
yearInception
Indicates the year in which something (such as an entity, event, or organization) was first established, created, or began.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 28, 2026, 6:33 a.m.