Triple
T36105105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foppe de Haan |
E1044331
|
entity |
| Predicate | tookSCHeerenveenTo |
P184679
|
FINISHED |
| Object | UEFA Champions League qualification |
E570978
|
NE 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: UEFA Champions League qualification | Statement: [Foppe de Haan, tookSCHeerenveenTo, UEFA Champions League qualification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookSCHeerenveenTo Context triple: [Foppe de Haan, tookSCHeerenveenTo, UEFA Champions League qualification]
-
A.
Sneekweek
Indicates participation in or association with the Dutch student sailing and water sports event known as Sneekweek.
-
B.
DutchSide
Indicates that one entity is located on, associated with, or belongs to the Dutch side of a border, region, or divided area in relation to another entity.
-
C.
AmsterdamAdmiralsScore
Indicates that the Amsterdam Admirals achieved a particular score in a game or match.
-
D.
bronVoor
Indicates that something serves as the source or origin from which another thing is derived or obtained.
-
E.
succeededByInHolland
Indicates that one entity is directly followed or replaced by another entity in a succession specific to Holland.
- F. None of above. chosen
Provenance (5 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_69f76e338e2c8190b7f3bc68bec76349 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b3e2f3c08190be4fd1ae4fa1266d |
completed | May 3, 2026, 8:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38d552a26481909710c1f5adebcb3d |
completed | June 22, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_69f7b1bcc47081909fe7d592ac69006c |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b3e0f1c88190985feab6cee8b05e |
completed | May 3, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:08 p.m.