Triple
T26796792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RKV (MARC) |
E670974
|
entity |
| Predicate | hasCodeString |
P196897
|
FINISHED |
| Object | RKV |
—
|
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: RKV | Statement: [RKV (MARC), hasCodeString, RKV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCodeString Context triple: [RKV (MARC), hasCodeString, RKV]
-
A.
hasCodeName
Indicates that an entity is known or referred to by a particular alternative name or alias, often used for secrecy or distinction.
-
B.
hasCodeIn
Indicates that one entity is represented, defined, or implemented within the codebase or coding context of another entity.
-
C.
codeString
Indicates that an entity is associated with a specific code represented as a string value.
-
D.
hasCodeContext
Indicates that an entity is associated with or occurs within a particular programming or code-related context.
-
E.
hasCodeLetters
Indicates that an entity is associated with, or represented by, a specific sequence of letters used as its code or identifier.
- 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_69eeb31fbd888190a82dac5822e453bc |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fe6e492bf8819080b25221d13445ea |
completed | May 8, 2026, 11:14 p.m. |
| PD | Predicate disambiguation | batch_69fe6dd33a6881908fe9bbbc184cab51 |
completed | May 8, 2026, 11:12 p.m. |
| PDg | Predicate description generation | batch_69fe6e4801108190a6be6bec2d52a1b9 |
completed | May 8, 2026, 11:14 p.m. |
Created at: April 27, 2026, 4:20 a.m.