Triple
T34224705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cardhu |
E878013
|
entity |
| Predicate | legalDistillationBegan |
P149390
|
FINISHED |
| Object | 1824 |
—
|
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: 1824 | Statement: [Cardhu, legalDistillationBegan, 1824]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalDistillationBegan Context triple: [Cardhu, legalDistillationBegan, 1824]
-
A.
legalDistillationLicenseYear
chosen
Indicates the year in which a legal license was granted or valid for operating a distillation activity.
-
B.
legalTermStart
Indicates that a specified legal term, period, or contractual timeframe begins at a particular point in time.
-
C.
legalPrecedentInvolved
Indicates that a particular legal precedent (prior court decision or ruling) is relevant to, cited in, or forms the basis for the current legal matter or action.
-
D.
legalFoundationPeriod
Indicates the time span during which a legal foundation, basis, or framework is formally valid or in effect.
-
E.
legalOpinionsIssuedOn
Indicates that one or more legal opinions were formally issued or rendered on a particular date, case, matter, or subject.
- 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_69f349b16d0481908754e3069f05e0c1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff5285ed74819097e6e2a9084a079a |
completed | May 9, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69ff51fbe28881908ac8417dff9db81a |
completed | May 9, 2026, 3:25 p.m. |
Created at: May 1, 2026, 1:55 a.m.