Triple
T32796902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | doctrine of discovery in U.S. law |
E838790
|
entity |
| Predicate | articulatedInYear |
P86624
|
FINISHED |
| Object | 1823 |
—
|
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: 1823 | Statement: [doctrine of discovery in U.S. law, articulatedInYear, 1823]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: articulatedInYear Context triple: [doctrine of discovery in U.S. law, articulatedInYear, 1823]
-
A.
articulatedInDocumentYear
Indicates that something is expressed, stated, or formally presented in a document created or associated with a specific year.
-
B.
hasPartInYear
Indicates that something includes or contains a specific part, component, or segment that is associated with a particular year.
-
C.
statedInYear
chosen
Indicates that something was declared, expressed, or formally stated during a specific calendar year.
-
D.
definedInYear
Indicates that something (such as an entity, concept, or item) was formally established, specified, or created in a particular calendar year.
-
E.
elaboratedInYear
Indicates that something was further developed, detailed, or expanded upon in a specific calendar year.
- 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_69f3493c7f6881908edf2aa13631d1e0 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:14 a.m.