Triple
T7285369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kolmanskop |
E163851
|
entity |
| Predicate | prosperityPeak |
P5317
|
FINISHED |
| Object | 1910s |
—
|
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: 1910s | Statement: [Kolmanskop, prosperityPeak, 1910s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prosperityPeak Context triple: [Kolmanskop, prosperityPeak, 1910s]
-
A.
prosperedFrom
Indicates that one entity gained benefit, success, or advantage as a result of another entity, event, or circumstance.
-
B.
historicalPeriodOfProsperity
chosen
Indicates a time span in which a society, region, or entity experienced notable economic growth, stability, and overall flourishing.
-
C.
apexOf
Indicates that one entity is the highest or most extreme point, level, or culmination of another entity or process.
-
D.
prominence
Indicates that an entity stands out in importance, visibility, or influence relative to others within a given context.
-
E.
growthProperty
Indicates that one entity characterizes, constrains, or quantifies how another entity grows or changes in magnitude over some parameter (such as time, size, or input).
- 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_69c6886093b88190a254b1ce6db8bae7 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb51a8bc8190a3e1ec09ee1aeb38 |
completed | March 27, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69c6e76c5fbc8190b378830082f11cb0 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:59 p.m.