Triple
T25723565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ANILCA |
E645054
|
entity |
| Predicate | expandedExistingUnitType |
P160934
|
FINISHED |
| Object | wilderness area |
—
|
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: wilderness area | Statement: [ANILCA, expandedExistingUnitType, wilderness area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expandedExistingUnitType Context triple: [ANILCA, expandedExistingUnitType, wilderness area]
-
A.
expandedExistingUnitType
chosen
Indicates that an existing unit type has been enlarged, extended, or otherwise increased in capacity or scope.
-
B.
expansionUnit
Indicates a unit or component that serves to extend, enlarge, or add capacity to another system, structure, or entity.
-
C.
expansionType
Indicates the specific manner or category by which something grows, extends, or increases in scope or size.
-
D.
basedUnitType
Indicates that one unit is defined or derived in terms of another underlying (base) unit type.
-
E.
extensionType
Indicates the specific kind or category of extension that characterizes how something is extended or augmented beyond its base form.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 21, 2026, 10:07 p.m.