Triple
T34280743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murray v. The Charming Betsy |
E879582
|
entity |
| Predicate | hasCranchCitation |
P101148
|
FINISHED |
| Object | 2 Cranch 64 |
—
|
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: 2 Cranch 64 | Statement: [Murray v. The Charming Betsy, hasCranchCitation, 2 Cranch 64]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCranchCitation Context triple: [Murray v. The Charming Betsy, hasCranchCitation, 2 Cranch 64]
-
A.
hasCitationForm
Indicates that an entity is associated with a specific standardized form used for citing or referencing it.
-
B.
hasCitationInformation
chosen
Indicates that an entity is associated with specific citation details, such as source, reference, or bibliographic information.
-
C.
citationOf
Indicates that one entity cites, references, or formally acknowledges another entity as a source.
-
D.
hasCitationStatus
Indicates the current citation-related state or condition assigned to a referenced work or source (e.g., cited, uncited, pending, or deprecated).
-
E.
hasCitationName
Indicates that an entity is associated with a specific name or label used when citing it in references or bibliographies.
- 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_69f349b5f6648190b9420d94a4cd16e0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 1, 2026, 1:57 a.m.