Triple
T1167121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Increase |
E24822
|
entity |
| Predicate | historicalUsageContext |
P1409
|
FINISHED |
| Object | colonial America |
—
|
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: colonial America | Statement: [Increase, historicalUsageContext, colonial America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalUsageContext Context triple: [Increase, historicalUsageContext, colonial America]
-
A.
historicalPeriodOfUse
Indicates the time period during which something was in active use or commonly utilized.
-
B.
hasHistoricalContext
chosen
Indicates that something is related to, influenced by, or best understood in light of specific past events, conditions, or time periods.
-
C.
historicallyUsedFor
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
-
D.
historicUsePersistsIn
Indicates that a practice, feature, or condition originating in the past continues to exist or be applied in the present.
-
E.
hasHistoriographicalUse
Indicates that something is used or cited within historical writing or analysis as part of constructing, interpreting, or debating historical narratives.
- 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_69a494082a7c819095004f423f294a64 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bccd75048190b8ce88237c1a748b |
completed | March 1, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69a4bb548c1481909092626c572d8782 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.