Triple
T21639600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CNXMN |
E534054
|
entity |
| Predicate | codeComponent |
P86070
|
FINISHED |
| Object | CN (country code) |
—
|
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: CN (country code) | Statement: [CNXMN, codeComponent, CN (country code)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeComponent Context triple: [CNXMN, codeComponent, CN (country code)]
-
A.
codeComponent1
chosen
Indicates that one entity is a specific code component (such as a function, class, or module) within a software system.
-
B.
codenameComponent
Indicates that one entity serves as the codename or code-designation assigned to another entity as its component or identifying label.
-
C.
scriptComponentOf
Indicates that one entity is a script that functions as a component or module within another entity (such as a system, application, or larger script).
-
D.
code
Indicates that an entity writes, develops, or produces computer software or source code.
-
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.
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_69e0c465ae7481908577b7209fdb2a77 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef5390ba7481908f58230779e5b7bb |
completed | April 27, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69e69677b9c48190bf81f795aa8ad74e |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:35 p.m.