Triple
T14661936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E.D. La. |
E344265
|
entity |
| Predicate | subjectAbbreviationContext |
P62615
|
FINISHED |
| Object | Bluebook legal citation |
—
|
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: Bluebook legal citation | Statement: [E.D. La., subjectAbbreviationContext, Bluebook legal citation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectAbbreviationContext Context triple: [E.D. La., subjectAbbreviationContext, Bluebook legal citation]
-
A.
academicTitleAbbreviation
Indicates that one entity is the standard abbreviated form of another entity’s full academic title.
-
B.
typeOfAbbreviation
Indicates that one term is an abbreviation of a specific type or category (e.g., acronym, initialism) of another expression.
-
C.
authorAbbreviation
Indicates that one entity is the standardized abbreviated form of an author's name used in citations or references for another entity.
-
D.
abbreviationContext
chosen
Indicates that one term is used as an abbreviation specifically within the contextual scope defined by another term or resource.
-
E.
abbreviationOrShortForm
Indicates that one term is an abbreviation or shortened form of another term.
- 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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb51c84448190a1f5fa9ab8a1e2c4 |
completed | April 14, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:27 a.m.