Triple
T37430190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alicante Bouschet |
E930112
|
entity |
| Predicate | crossYearApproximate |
P192613
|
FINISHED |
| Object | mid-19th century |
—
|
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: mid-19th century | Statement: [Alicante Bouschet, crossYearApproximate, mid-19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossYearApproximate Context triple: [Alicante Bouschet, crossYearApproximate, mid-19th century]
-
A.
transitionYear
Indicates the specific year in which a change, shift, or transition from one state, condition, or phase to another occurs.
-
B.
coversYearsTo
Indicates a temporal relationship where one entity spans, includes, or extends up to a specified year or range of years represented by the other entity.
-
C.
crossErectedInYear
Indicates that a particular cross was erected or put in place in a specified year.
-
D.
divisionYear
Indicates the year in which a division or split of an entity took place.
-
E.
retitleApproxYear
Indicates that an entity was retitled or renamed around an approximate year, rather than at a precisely known date.
- 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_69f76ebf0f288190ba198a78341613b8 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
| PDg | Predicate description generation | batch_69fd19f6a7888190aa7eee2b87687c53 |
completed | May 7, 2026, 11:02 p.m. |
Created at: May 3, 2026, 4:17 p.m.