Triple
T14013764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WLW |
E337152
|
entity |
| Predicate | historicHighPowerEra |
P112447
|
FINISHED |
| Object | 1930s |
—
|
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: 1930s | Statement: [WLW, historicHighPowerEra, 1930s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicHighPowerEra Context triple: [WLW, historicHighPowerEra, 1930s]
-
A.
historicalEraOfSuccess
Indicates that an entity achieved notable success or prominence during a specified historical era.
-
B.
historicalEraOfRise
Indicates the historical era or period during which an entity first rose to prominence, influence, or significance.
-
C.
historical era
Indicates the broad historical period or epoch during which an entity, event, or phenomenon took place or is associated.
-
D.
historicalPower
Indicates that one entity held significant influence, control, or authority over another during a past period.
-
E.
historicalEraOfIntenseSearch
Indicates a period in history characterized by particularly vigorous, widespread, or focused efforts to seek, discover, or investigate something.
- F. None of above. chosen
Provenance (4 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f37d11481909159bdb9e1e8d38e |
completed | April 14, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69de05a802ac819090604025aae6a4d5 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239524688190a0f2408c239cfcaa |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:19 p.m.