Triple
T5410542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nature |
E121001
|
entity |
| Predicate | lCCN |
P7023
|
FINISHED |
| Object | 07035224 |
—
|
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: 07035224 | Statement: [Nature, lCCN, 07035224]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lCCN Context triple: [Nature, lCCN, 07035224]
-
A.
lccn
chosen
Indicates that an entity is associated with a specific Library of Congress Control Number (LCCN), uniquely identifying its bibliographic record in the Library of Congress catalog.
-
B.
hasLccn
Indicates that an entity is associated with a specific Library of Congress Control Number (LCCN) as its unique identifier in the Library of Congress catalog.
-
C.
L2Is
Indicates that one entity is located at or occupies a specific level 2 (L2) position or layer relative to another entity.
-
D.
ICCCode
Indicates that an entity is associated with a specific International Criminal Court (ICC) code, identifying its classification or legal reference under ICC standards.
-
E.
hasCcf
Indicates that one entity possesses, is associated with, or is characterized by a specific CCF (the exact nature of which is defined elsewhere in the model or ontology).
- 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_69bd463a41cc8190b32ff5af2b96ca93 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87985ee0819092a9a5cd6a948138 |
completed | March 20, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69bd8467e6b48190b9eaa9de67072e06 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:05 p.m.