Triple
T22297163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Krusenstern National Monument |
E551149
|
entity |
| Predicate | timeDepthOfHumanUse |
P63523
|
FINISHED |
| Object | over 5000 years |
—
|
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: over 5000 years | Statement: [Cape Krusenstern National Monument, timeDepthOfHumanUse, over 5000 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeDepthOfHumanUse Context triple: [Cape Krusenstern National Monument, timeDepthOfHumanUse, over 5000 years]
-
A.
historicalPeriodOfUse
Indicates the time period during which something was in active use or commonly utilized.
-
B.
historicalPeriodOfGreatestUse
Indicates the time period during which something was used most intensively or prevalently.
-
C.
timeDepthOfLandUse
chosen
Indicates the duration or historical depth over which a particular land use has been present or practiced in a given area.
-
D.
historicUsePersistsIn
Indicates that a practice, feature, or condition originating in the past continues to exist or be applied in the present.
-
E.
historicalPeriodOfFirstUse
Indicates the historical time period during which something was first used or came into use.
- 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_69e11e45fb848190a1b2ae21296e3a5f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15720fba0819080f6c96f6df4f1e0 |
completed | April 29, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:41 p.m.