Triple
T8773283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IN-KL |
E208516
|
entity |
| Predicate | fullCode |
P85320
|
FINISHED |
| Object | IN-KL |
—
|
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: IN-KL | Statement: [IN-KL, fullCode, IN-KL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullCode Context triple: [IN-KL, fullCode, IN-KL]
-
A.
codeFor
Indicates that one entity serves as the implementation, encoding, or programmatic representation for another entity.
-
B.
code
Indicates that an entity writes, develops, or produces computer software or source code.
-
C.
productionCode
Indicates the unique identifier or code assigned to a specific production (such as a film, TV episode, or manufactured item) that links related records or versions of that production.
-
D.
swiftCode
Indicates that a financial institution is identified or associated with a specific SWIFT/BIC code used for international banking transactions.
-
E.
codeSpace
Indicates the namespace or contextual scope within which a piece of code, identifier, or programming element is defined and interpreted.
- 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_69ca835edb4481909b4aafb616dc5eb7 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f2dc87c8190be0597a260d95a0b |
completed | March 31, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1aff3881908be6a9cbc9f50461 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cfddef48190aee764ee7b25bae9 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:41 p.m.