Triple
T35775062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carolina Gold Belt |
E1034267
|
entity |
| Predicate | declineInProduction |
P66808
|
FINISHED |
| Object | after California Gold Rush |
—
|
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: after California Gold Rush | Statement: [Carolina Gold Belt, declineInProduction, after California Gold Rush]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: declineInProduction Context triple: [Carolina Gold Belt, declineInProduction, after California Gold Rush]
-
A.
declineIn
chosen
Indicates a relationship where one entity experiences a decrease or reduction in the level, amount, or intensity of another entity over time.
-
B.
decline
Indicates a decrease or reduction in the level, amount, quality, or intensity of something over time.
-
C.
decliningAs
Indicates that one entity is decreasing in value, intensity, or importance relative to another over time.
-
D.
declineAfter
Indicates that one entity or value decreases or worsens following another specified event, condition, or point in time.
-
E.
declineOrEnd
Indicates that a relationship, process, or state is either decreasing in intensity or coming to a complete end.
- 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_69f76e14a1e081908eddd57bd6fdb3be |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a1fb893081909e865c1f11ce221e |
completed | May 3, 2026, 7:28 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.