Triple
T36750263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CLARI |
E907888
|
entity |
| Predicate | codePart1 |
P115944
|
FINISHED |
| Object | CL |
—
|
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: CL | Statement: [CLARI, codePart1, CL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codePart1 Context triple: [CLARI, codePart1, CL]
-
A.
hasPart1Code
chosen
Indicates that an entity includes or is associated with a specific part identified by a particular code.
-
B.
codeSecondPart
Indicates that the entity represents the second part or segment of a larger code.
-
C.
codeComponent1
Indicates that one entity is a specific code component (such as a function, class, or module) within a software system.
-
D.
firstPartValue
Indicates that the subject entity represents the initial or leading portion of a larger value, sequence, or composite data item.
-
E.
firstPartType
Indicates that one entity is the initial segment or component type within a larger composite or sequence of parts.
- 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_69f76e76d10881909ec1679bc043108c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.