Triple
T22050530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Principles (Topic 105) |
E544869
|
entity |
| Predicate | hasCodificationNumber |
P58073
|
FINISHED |
| Object | 105 |
—
|
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: 105 | Statement: [General Principles (Topic 105), hasCodificationNumber, 105]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCodificationNumber Context triple: [General Principles (Topic 105), hasCodificationNumber, 105]
-
A.
codifiedIn
Indicates that something is formally recorded, defined, or established within a specific document, code, or legal/institutional text.
-
B.
codificationTopicNumber
chosen
Indicates the numbered topic or subject under which something is organized or classified in a codification system.
-
C.
codificationLevel
Indicates the degree or extent to which something is formally systematized, standardized, or encoded into an explicit set of rules or structures.
-
D.
codifiedUnderAuthority
Indicates that something has been formally established, defined, or recorded according to the rules or power of a specific authority.
-
E.
hasDesignationNumber
Indicates that an entity is associated with a specific official designation or identification number.
- 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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1283386f081908b70df81f38a5b1c |
completed | April 28, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e6f643ca74819083e8ab78e843f243 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:26 p.m.