Triple
T38610070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mountain Timber Co. v. Washington |
E934452
|
entity |
| Predicate | UScitation |
P24251
|
FINISHED |
| Object | 243 U.S. 219 |
—
|
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: 243 U.S. 219 | Statement: [Mountain Timber Co. v. Washington, UScitation, 243 U.S. 219]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UScitation Context triple: [Mountain Timber Co. v. Washington, UScitation, 243 U.S. 219]
-
A.
uscCitation
chosen
Indicates that one legal authority cites or references a provision of the United States Code (U.S.C.).
-
B.
citationAct
Indicates an act in which one entity cites, references, or otherwise acknowledges another entity as a source or authority.
-
C.
legalCitationSystem
Indicates a system or convention used to reference and identify legal authorities such as cases, statutes, or regulations.
-
D.
citationAs
Indicates that one entity is cited or referenced in the role or capacity specified by another entity (such as a particular work, version, or context).
-
E.
citationIn
Indicates that one work cites, references, or otherwise acknowledges another work as a source.
- 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_69f76eccd6d081909ccce171011739a1 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.