Triple
T11656851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joltid |
E277030
|
entity |
| Predicate | associatedWith |
P37
|
FINISHED |
| Object | Joost |
E277031
|
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: Joost | Statement: [Joltid, associatedWith, Joost]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Joost Context triple: [Joltid, associatedWith, Joost]
-
A.
Joost
Joost is a masculine given name of Dutch origin, historically associated with figures such as the poet and playwright Joost van den Vondel.
-
B.
Joost
chosen
Joost was an online video distribution service and Internet TV platform co-created by Skype and Kazaa co-founder Niklas Zennström.
-
C.
Joost Lips
Joost Lips was a Flemish humanist and classical scholar of the late Renaissance, renowned for his influential works on Stoic philosophy and Roman history.
-
D.
Jelle
Jelle is a Dutch given name commonly used for males, particularly in the Netherlands and Friesland.
-
E.
Joost Vos
Joost Vos is a Dutch architect best known as a leading partner at the renowned architecture firm Benthem Crouwel Architekten, contributing to major public and infrastructural projects.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d0331481909682b2e504e4c9a0 |
completed | April 10, 2026, 7:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ee88166900819095063f045be44bed |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 8, 2026, 9:39 p.m.