Triple
T18867615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KV20 |
E461480
|
entity |
| Predicate | hasKVDesignation |
P133251
|
FINISHED |
| Object | KV20 |
—
|
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: KV20 | Statement: [KV20, hasKVDesignation, KV20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKVDesignation Context triple: [KV20, hasKVDesignation, KV20]
-
A.
hasDesignation
Indicates that an entity holds or is assigned a specific title, label, or formal designation.
-
B.
hasInternalDesignationFor
Indicates that one entity assigns or uses an internal label, code, or designation to refer to another entity.
-
C.
hasDesignationBy
Indicates that one entity has been formally assigned or labeled with a specific designation by another entity.
-
D.
hasDesignationForm
Indicates that an entity is associated with a particular form or format used for its designation or naming.
-
E.
hasLetterDesignation
Indicates that an entity is assigned or associated with a specific letter-based designation or code.
- 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c2a6d1d081909b6dab2a5166a317 |
completed | April 20, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69e48d2166b88190add38de96cedc65c |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:57 a.m.