Triple
T14481325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KV7 |
E359107
|
entity |
| Predicate | hasKVNumber |
P114370
|
FINISHED |
| Object | KV7 |
—
|
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: KV7 | Statement: [KV7, hasKVNumber, KV7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKVNumber Context triple: [KV7, hasKVNumber, KV7]
-
A.
keyValue
Indicates that one entity functions as a key that is associated with a corresponding value represented by the other entity.
-
B.
hasReplicationNumber
Indicates that an entity is associated with a specific replication or copy number, typically quantifying how many instances or reproductions of it exist.
-
C.
hasLevelNumber
Indicates that an entity is associated with a specific level identified by a numerical value.
-
D.
hasKeyQuantity
Indicates that an entity is associated with a primary or defining quantity that characterizes or measures it.
-
E.
keySpaceSize
Indicates the total number of distinct keys that can exist within a given key space or key domain.
- 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de924bc548819087a2f693840d7426 |
completed | April 14, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c487b4c819097803e58dca628a5 |
completed | April 14, 2026, 3:24 p.m. |
| PDg | Predicate description generation | batch_69de5fb4de14819092acdecbd201d672 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:20 a.m.