Triple
T27228590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Scenic Trail |
E682084
|
entity |
| Predicate | legalBasisYear |
P91135
|
FINISHED |
| Object | 1968 |
—
|
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: 1968 | Statement: [National Scenic Trail, legalBasisYear, 1968]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalBasisYear Context triple: [National Scenic Trail, legalBasisYear, 1968]
-
A.
legalBasis
Indicates the legal rule, authority, or justification under which an action, decision, or status is established or carried out.
-
B.
legalBasisConsidered
Indicates that a decision, action, or assessment has taken into account the relevant legal grounds, statutes, or regulations as part of its justification.
-
C.
legalCodeIssuedInYear
chosen
Indicates the year in which a particular legal code was formally issued or enacted.
-
D.
legalFoundationPeriod
Indicates the time span during which a legal foundation, basis, or framework is formally valid or in effect.
-
E.
hasLegalBasisSince
Indicates that something has had a valid legal foundation or authority starting from a specified point in time.
- 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_69eefacdad7881908b7bca61c90a1a1e |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: April 27, 2026, 9:45 a.m.