Triple
T24681062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NAC Breda |
E611129
|
entity |
| Predicate | NOADExpansion |
P42398
|
FINISHED |
| Object | Nooit Opgeven Altijd Doorzetten |
—
|
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: Nooit Opgeven Altijd Doorzetten | Statement: [NAC Breda, NOADExpansion, Nooit Opgeven Altijd Doorzetten]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NOADExpansion Context triple: [NAC Breda, NOADExpansion, Nooit Opgeven Altijd Doorzetten]
-
A.
acronymExpansion
chosen
Indicates that one term is an acronym whose letters stand for the words in another, longer expression.
-
B.
englishNetwork
Indicates that there is a network-based relationship or connection specifically involving the English language between the related entities.
-
C.
wordDefinition
Indicates that one entity provides the meaning or explanation of a word represented by the other entity.
-
D.
expands
Indicates that one entity increases in size, volume, scope, or extent relative to a previous state or another entity.
-
E.
hasMeaningExtension
Indicates that one entity represents an extended, elaborated, or more detailed meaning of another entity’s meaning.
- 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_69e2c4d5c2dc8190ac857dea25ec6ce9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 3:10 a.m.