Triple
T485133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Title 33 of the United States Code |
E9857
|
entity |
| Predicate | hasCitationAbbreviation |
P8075
|
FINISHED |
| Object | 33 U.S.C. |
—
|
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: 33 U.S.C. | Statement: [Title 33 of the United States Code, hasCitationAbbreviation, 33 U.S.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCitationAbbreviation Context triple: [Title 33 of the United States Code, hasCitationAbbreviation, 33 U.S.C.]
-
A.
citationNumber
Indicates the specific numeric identifier assigned to a citation within a document or reference list.
-
B.
hasNameAbbreviation
chosen
Indicates that an entity is associated with a shortened or abbreviated form of its full name.
-
C.
citesAs
Indicates that one entity references or acknowledges another as a source of information, authority, or evidence.
-
D.
hasBibliographicCategory
Indicates that an entity is associated with a specific bibliographic classification or category within a cataloging or documentation system.
-
E.
citationBy
Indicates that one work is cited or referenced by another work.
- 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_69a2e802e2908190ab17c9479e0b6412 |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f0bb46788190b40182bf2a54f98f |
completed | Feb. 28, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69a2edf48ec08190b85d07e194f99c49 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.