Triple
T137255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Library of Congress Classification |
E2773
|
entity |
| Predicate | usesNotationType |
P3759
|
FINISHED |
| Object | alphanumeric notation |
—
|
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: alphanumeric notation | Statement: [Library of Congress Classification, usesNotationType, alphanumeric notation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesNotationType Context triple: [Library of Congress Classification, usesNotationType, alphanumeric notation]
-
A.
notationType
chosen
Indicates the specific system or style of notation used to represent or encode something (such as music, math, or language).
-
B.
usesStandard
Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
-
C.
doesNotUse
Indicates that one entity intentionally refrains from employing, utilizing, or relying on another entity, method, or resource.
-
D.
usesElement
Indicates that one entity makes use of, incorporates, or depends on a specified element in its structure, function, or behavior.
-
E.
usesNamingSystem
Indicates that one entity adopts or applies a particular naming system or convention to identify or label other entities.
- 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_69a2521e35c08190b28e5c9f1e3c9b59 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a257a6cab88190944c8f74d8d1605c |
completed | Feb. 28, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69a25652efdc8190b85b33735a9e6370 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.