Triple
T14324762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Year’s Dive |
E355186
|
entity |
| Predicate | hasVariantsIn |
P113983
|
FINISHED |
| Object | other Dutch coastal towns |
—
|
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: other Dutch coastal towns | Statement: [New Year’s Dive, hasVariantsIn, other Dutch coastal towns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVariantsIn Context triple: [New Year’s Dive, hasVariantsIn, other Dutch coastal towns]
-
A.
hasVariant
Indicates that one entity exists as an alternative form, version, or variation of another entity.
-
B.
hasVariantSeries
Indicates a relationship where one entity is a variant or alternative series derived from or associated with another series.
-
C.
hasCommercialVariant
Indicates that an entity has a related version that is produced, marketed, or sold commercially.
-
D.
hasVariantFamily
Indicates that one entity is related to another as a different version, type, or family variant of it.
-
E.
hasVariantSystem
Indicates that one system is an alternative or variant form of another system within the same general framework or category.
- 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de883e6a288190b6c22f630a1eef3c |
completed | April 14, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69de2a9515f4819081aabf251bca5878 |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e9ded24819099200349cf80e068 |
completed | April 14, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:13 a.m.