Triple
T5030600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Land van Cuijk |
E113289
|
entity |
| Predicate | flagUsedFrom |
P19687
|
FINISHED |
| Object | 2022 |
—
|
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: 2022 | Statement: [Land van Cuijk, flagUsedFrom, 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flagUsedFrom Context triple: [Land van Cuijk, flagUsedFrom, 2022]
-
A.
flagUsedBy
chosen
Indicates that a particular flag is officially used by a specified entity, such as a country, organization, or group.
-
B.
flagUsedIn
Indicates that a particular flag is employed or referenced within a given context, such as a program, configuration, or process.
-
C.
flag
Indicates that one entity marks, signals, or draws attention to another entity, often to denote status, importance, or the need for review or action.
-
D.
flagOrigin
Indicates the place or source from which a flag originates or is derived.
-
E.
flagVersion
Indicates that one entity serves as a specific version or revision of a flag associated with another entity.
- 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_69bd443775e48190a646ffbfc4334723 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73922a4c81908651c2d9b5e01cb6 |
completed | March 20, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69bd71509e9c8190a60c1d8d04936a12 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:36 p.m.